lists.openwall.net   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  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E1D0117.2030707@tao.ma>
Date:	Wed, 13 Jul 2011 10:21:11 +0800
From:	Tao Ma <tm@....ma>
To:	Greg KH <greg@...ah.com>
CC:	linux-ext4@...r.kernel.org, Jan Kara <jack@...e.cz>,
	Corrado Zoccolo <czoccolo@...il.com>,
	Jeff Moyer <jmoyer@...hat.com>,
	Jens Axboe <jaxboe@...ionio.com>, stable@...nel.org,
	Vivek Goyal <vgoyal@...hat.com>
Subject: Re: [stable] [PATCH] jbd/2[stable only]: Use WRITE_SYNC_PLUG in journal_commit_transaction.

On 07/13/2011 10:17 AM, Greg KH wrote:
> On Wed, Jul 13, 2011 at 10:10:03AM +0800, Tao Ma wrote:
>> On 07/12/2011 11:55 PM, Greg KH wrote:
>>> On Tue, Jul 12, 2011 at 06:43:51PM +0800, Tao Ma wrote:
>>>> This only affects .37 and .38 since Jens' new plug patches are included
>>>> in .39 and the bug is removed as a side effect. But I think it is needed
>>>> anyway for the stable. And RHEL6 needs this also I guess.
>>>
>>> Both the .37 and .38-stable kernel trees are end-of-life and not having
>>> any more releases, so there's no tree for these to be applied too,
>>> sorry.
>> Fine. Since RHEL6 still has this problem(not sure SLES has this problem
>> or not), I may add a bug in redhat's bugzilla.
> 
> Ok, but neither RHEL6 or SLES11 is based on .37 or .38, so it might not
> be relevant for them either.
Thanks for the reminder.
Actually I used RHEL6.1 and it seems that Corrado's patch 749ef9f8423 is
backported by redhat's guy already since it does have the problem I
mentioned.

Thanks
Tao
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ