----------------------------------------
> Date: Tue, 27 Sep 2011 15:35:23 -0400
> From: tytso@xxxxxxx
> To: konrad.wilk@xxxxxxxxxx
> CC: tinnycloud@xxxxxxxxxxx; linux-ext4@xxxxxxxxxxxxxxx;
> xen-devel@xxxxxxxxxxxxxxxxxxx; jack@xxxxxxx
> 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@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home