>>> On 27.09.11 at 04:22, MaoXiaoyun <tinnycloud@xxxxxxxxxxx> wrote: > > > ---------------------------------------- >> Date: Mon, 26 Sep 2011 10:28:08 -0400 >> From: konrad.wilk@xxxxxxxxxx >> To: tinnycloud@xxxxxxxxxxx >> CC: linux-ext4@xxxxxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxx; tytso@xxxxxxx; > jack@xxxxxxx >> Subject: Re: [patch 1/1] ext4-fix-dirty-extent-when-origin-leaf-extent-reac.patch >> >> On Sun, Sep 25, 2011 at 04:45:39PM +0800, MaoXiaoyun wrote: >> > >> > >> > Hi: >> > >> > We met an ext4 BUG_ON in extents.c:1716 which crash kernel flush thread, > and result in disk unvailiable. >> > >> > BUG details refer to: > http://www.gossamer-threads.com/lists/xen/devel/217091?do=post_view_threaded >> > >> > 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? >> > > The patch is for 2.6.39. It can be patched on 2.6.32 too. > Thanks. So why don't you suggest applying this to the stable tree maintainers instead? xen-devel really isn't the right forum for this sort of bug fixes, particularly when the underlying kernel.org tree is still being maintained. Jan >> > >> > Without this patch, more than 3 servers hit BUG_ON in our hundreds of > servers every day. >> > >> > >> > many thanks. >> >> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-devel -- 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
