Comment 4 for bug 389555

According to <http://lkml.org/lkml/2009/4/30/545>, there will not be any more 2.6.28 stable releases. However, there have been three 2.6.27 releases since then, the latest of which includes this patch along with a bunch of other ext4 patches. Would it be worthwhile to ask upstream (Greg KH?) to cherrypick the ext4 patches into a new 2.6.28.11 release so that you don't have to maintain this patch locally?

Also, could this be related to the ext4 filesystem corruption reported in bug #346691? I see that this patch fixes a longstanding ext4 bug, whereas bug #346691 is relatively new; perhaps a recent kernel change causes this bug to be tickled much more frequently?