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]
Date:	Wed, 28 Sep 2011 12:09:39 +0800
From:	MaoXiaoyun <tinnycloud@...mail.com>
To:	<tytso@....edu>, <konrad.wilk@...cle.com>
CC:	<linux-ext4@...r.kernel.org>,
	xen devel <xen-devel@...ts.xensource.com>, <jack@...e.cz>,
	<jeremy@...p.org>
Subject: RE: [patch 1/1]
 ext4-fix-dirty-extent-when-origin-leaf-extent-reac.patch




----------------------------------------
> Date: Tue, 27 Sep 2011 15:35:23 -0400
> From: tytso@....edu
> To: konrad.wilk@...cle.com
> CC: tinnycloud@...mail.com; linux-ext4@...r.kernel.org; xen-devel@...ts.xensource.com; jack@...e.cz
> Subject: Re: [patch 1/1] ext4-fix-dirty-extent-when-origin-leaf-extent-reac.patch
>
> On Mon, Sep 26, 2011 at 10:28:08AM -0400, Konrad Rzeszutek Wilk wrote:
> > >
> > > Attached is the fix, verified in our env.
> >
> > So.. you are asking for this upstream git commit to be back-ported
> > to 2.6.32, right?
>
> I'm curious --- is there a good reason why Xen users are using an
> upstream 2.6.32 kernel? If they are using a distro kernel, fine, but
> then the distro kernel should be providing the support. But at this
> point, 2.6.32 is so positively *ancient* that, I'm personally not
> interesting in providing free, unpaid distro support for users who
> aren't willing to either (a) pay $$$ and get a supported distro
> kernel, or (b) use a much more modern kernel. At this point, Guest
> and Host Xen support is available in 3.0 kernels, so there's really no
> excuse, right?

Mmm...
 
We first met this bug at pvops kernel(jeremy's tree, 2.6.32.36). 
 
We failed to find any related fix from google, so we debug the bug ourself.
Fortunately, we located root cause and thought some other xen users might
have this problem as well, that's why we sent out the fix to Xen-devel.
 
We go through the code from 2.6.32 - 2.6.39, this bug exists.
People who use *ancient* kernel need this. 
 
Thanks.

> - Ted
> --
> 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 		 	   		  
--
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