On Tue, 2008-04-01 at 17:07 -0400, J. Bruce Fields wrote: > On Fri, Mar 28, 2008 at 03:20:18PM +0200, Meelis Roos wrote: > > Current 2.6.25-rc* kernels have broken am-utils (NFS-based automounter) > > support. No error messages, just "no such file or directory" when trying > > to enter /net/anotherhostname. Just tried 2.6.24 and that worked fine. > > am-utils is the latest in Debian unstable, 6.1.5-9. > > > > Earliest 2.6.25-rc currently tested was 2.6.25-rc3+git as of 20080304. > > This version reports > > Invalid hostname "pid3477@koiott:/net" in NFS lock request > > into dmesg and am-utils does not work. > > > > 2.6.25-rc4+git as of 20080310 and later ones do not show this message > > but am-utils does still not work. > > > > Will try bisecting it further. > > Have you figured out anything more? Can strace show exactly which > system call is failing? See the bugzilla report: http://bugzilla.kernel.org/show_bug.cgi?id=10349 I'm still waiting to hear back from Meelis, but to me this looks like an am-utils bug. AFAICS, am-utils advertises a binary NFS mount structure version of '6', to the mount() syscall, but internally they only initialise the equivalent of a version '4' structure. When http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=f9c3a3802119a2d30f3e4a69aef30a81e09d0209 was merged, then this failure to initialise the selinux 'context' field causes mount() to return an EINVAL. Cheers Trond -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
