On Mon, 2006-10-09 at 12:32 +0100, David Howells wrote: > David Chinner <dgc@xxxxxxx> wrote: > > > > o turn it off by default in -mm and see what goes boom > > > > Will we even see the conditions for the NFS client to go boom in the > > environments -mm kernels are typically run? i.e. does someone have a > > test case that reliably triggers problems? > > I don't know about that, but we (Red Hat) have had customers logging the > problem in our Bugzilla against NFS. > > Coming up with a reliable test case is a little tricky, as it involves setting > up a server to generate fileids > 0xffffffff, and manipulating inode numbers > directly generally isn't allowed... Maybe it can be done with a ramfs hack. you can do a debug hack inside the kernel, where on 32 bit inode fs's you copy the lower 32 bit into the higher 32 bit (and maybe invert the bits or something); this can then be verified for all kinds of things all over the place ;) -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com - 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
