On Wed, 29 Apr 2009 08:39:22 -0400 Trond Myklebust <trond.myklebust@xxxxxxxxxx> wrote: > On Wed, 2009-04-29 at 09:45 +0200, Nick Piggin wrote: > > On Wed, Apr 29, 2009 at 12:24:18AM -0700, Andrew Morton wrote: > > > On Wed, 29 Apr 2009 09:12:33 +0200 Nick Piggin <npiggin@xxxxxxx> wrote: > > > > > > > I haven't got any prepared, but they should be a pretty trivial > > > > backport, provided we also backport c2ec175c39f62949438354f603f4aa170846aabb > > > > (which is probably a good idea anyway). > > > > > > > > However I will probably wait for a bit, given that the patch isn't upstream > > > > yet. > > > > > > err, I'd marked it as for-2.6.31. It looks like that was wrong? > > > > At the time I agreed because I didn't know the severity of the NFS > > bugs. So it is up to you and Trond / nfs guys I guess. > > > > The bug affects any serious use of shared mmap writes, so it's pretty > urgent to get it merged together with the NFS 3 liner. As I said in an > earlier email, I'm able to reproduce it at will within 1 minute or so of > using iozone with the right options. > > I also concur with the opinion that we should backport it to the stable > kernels as soon as possible. > ok... I don't know what the "NFS 3 liner" is, but I trust you'll take care of it. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
