On Fri, 2007-11-16 at 03:03 -0800, Chris Wedgwood wrote: > On Fri, Nov 16, 2007 at 10:17:17AM +0100, Christian Kujau wrote: > > > OK, I'll try this. I hope this can be fixed somehow before 2.6.24... > > Well, one simple nasty idea would be something like: > > diff --git a/fs/Kconfig b/fs/Kconfig > index 429a002..da231fd 100644 > --- a/fs/Kconfig > +++ b/fs/Kconfig > @@ -1604,7 +1604,7 @@ config NFS_FS > > config NFS_V3 > bool "Provide NFSv3 client support" > - depends on NFS_FS > + depends on NFS_FS && !XFS > help > Say Y here if you want your NFS client to be able to speak version > 3 of the NFS protocol. > > So people who are likely to be affect just side-step the issue until > it's resolved.
Very funny, but disabling XFS on the client won't help. Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
