Re: [Bug #17752] 2.6.36-rc3: inconsistent lock state (iprune_sem,shrink_icache_memory)

[Stefan Richter]

Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.35.  Please verify if it still should be listed and let the tracking team
> know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=17752
> Subject		: 2.6.36-rc3: inconsistent lock state (iprune_sem, shrink_icache_memory)
> Submitter	: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
> Date		: 2010-09-01 6:37 (20 days old)
> Message-ID	: <tkrat.ed8eda6bc8ffe64e@xxxxxxxxxxxxxxxxx>
> References	: http://marc.info/?l=linux-kernel&m=128332308528119&w=2

I think this should not be marked as a regression.  See the older reports of
very similar issues (in my LKML mail from September 3, logged in bugzilla in
comment #1)
	http://lkml.org/lkml/2010/1/15/76	(2.6.33-rc, xfs involved)
	http://lkml.org/lkml/2010/1/18/108	(2.6.32.y, ntfs involved)
and hch's analysis in the first of these two threads
	http://lkml.org/lkml/2010/1/19/267	(several filesystems and
						 other code paths)
So, unless my trace was a code path that only newly acquired that oldproblem
of other code paths, this is an older issue.  Alas this is not obvious to me
at least from the log that I got.

I did not have lockdep enabled on the machine which delivered the log during
the last few months or so; I just remembered to re-enable it at the occasion
of switching to 2.6.36-rc.
-- 
Stefan Richter
-=====-==-=- =--= =-=--
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/