linux-kernel - Re: User space automounter problems after upgrade to 2.6.25-rc9

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 15 Apr 2008 06:58:12 -0700 (PDT)
From:	Martin Knoblauch <spamtrap@...bisoft.de>
To:	Trond Myklebust <trond.myklebust@....uio.no>
Cc:	linux-kernel@...r.kernel.org, am-utils <am-utils@...utils.org>
Subject: Re: User space automounter problems after upgrade to 2.6.25-rc9

----- Original Message ----
> From: Trond Myklebust <trond.myklebust@....uio.no>
> To: Martin Knoblauch <spamtrap@...bisoft.de>
> Cc: linux-kernel@...r.kernel.org; am-utils <am-utils@...utils.org>
> Sent: Tuesday, April 15, 2008 2:57:26 PM
> Subject: Re: User space automounter problems after upgrade to 2.6.25-rc9
> 
> 
> On Tue, 2008-04-15 at 04:28 -0700, Martin Knoblauch wrote:
> > Hi,
> > 
> >  after booting a newly built 2.6.25-rc9 kernel, I see the following messages 
> and the user space automounter fails to work. Last good kernel for me is 2.6.24, 
> as -rc9 is my first attempt at 2.6.25. Extremely sorry for being late to the 
> game :-(
> > 
> > [   13.776876] Invalid hostname "pid4302@...dm60:/home" in NFS lock request
> > [   11.996757] Invalid hostname "pid4302@...dm60:/home" in NFS lock request
> > [   14.504927] Invalid hostname "pid4302@...dm60:/home" in NFS lock request
> > [   13.636860] Invalid hostname "pid4302@...dm60:/home" in NFS lock request
> > [   14.504927] Invalid hostname "pid4302@...dm60:/home" in NFS lock request
> > [   13.636860] Invalid hostname "pid4302@...dm60:/home" in NFS lock request
> > [   14.505079] Invalid hostname "pid4302@...dm60:/home" in NFS lock request
> > [   11.996757] Invalid hostname "pid4302@...dm60:/home" in NFS lock request
> > [   13.636860] Invalid hostname "pid4302@...dm60:/home" in NFS lock request
> > [   12.688801] Invalid hostname "pid4302@...dm60:/soft" in NFS lock request
> > 
> > am-utils version is 6.1.5, config is attached
> 
> Already reported in:
>    http://bugzilla.kernel.org/show_bug.cgi?id=10349
> and
>    https://bugzilla.am-utils.org/show_bug.cgi?id=612
> 
> The problem is due to known bugs in the am-utils mount code (no,
> 'pid4302@...dm60:/soft' is not and has never been a valid server
> hostname).
> 

 I always wondered, but never asked :-) Apparently the kernel did never care until recently.

> The workaround should be to turn off locking by adding the 'nolock'
> mount flag.
> 

 Not sure what kind of side effects that will have. Probably better to stay at 2.6.24 and wait for a fix in am-utils.

Cheers

Martin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/