On Wed, 9 Jan 2008, Andy Gospodarek wrote:
On Wed, Jan 09, 2008 at 09:54:56AM -0800, Jay Vosburgh wrote:
<CUT>
This should silence the lockdep (if I'm understanding what
everybody's saying), and keep the change set to a minimum. This might
The lockdep problem is easy to trigger. The lockdep code does a good
job of noticing problems quickly regardless of how easy the deadlocks
are to create.
Exactly. All I need to do is to reboot my server, I have 100% probability
to get the warning.
not even be worth pushing for 2.6.24; I'm not exactly sure how difficult
the lockdep problem would be to trigger.
I'd like to see it go in there (for correct-ness) and to avoid hearing
about these lockdep issues for the next few months until it makes it
into 2.4.25.
Right. So, what is the final patch? I would like to test it if that's
possible. ;)
Best regards,
Krzysztof Olędzki
