lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 12 Jan 2008 11:53:02 +0100 (CET)
From:	Krzysztof Oledzki <>
To:	Andy Gospodarek <>
cc:	Jay Vosburgh <>,,
	Jeff Garzik <>,
	David Miller <>,
	Herbert Xu <>
Subject: Re: [PATCH 0/3] bonding: 3 fixes for 2.6.24

On Wed, 9 Jan 2008, Andy Gospodarek wrote:
> On Wed, Jan 09, 2008 at 09:54:56AM -0800, Jay Vosburgh wrote:
>> 	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

Powered by blists - more mailing lists