linux-kernel - Re: 2.6.39-rc1 regression: NFS - unable to mount some shares (bisected)

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110331162338.GA32296@core.coreip.homeip.net>
Date:	Thu, 31 Mar 2011 09:23:38 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Dmitry Torokhov <dtor@...are.com>
Cc:	Bryan Schumaker <bjschuma@...app.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Trond Myklebust <Trond.Myklebust@...app.com>
Subject: Re: 2.6.39-rc1 regression: NFS - unable to mount some shares
 (bisected)

Hi Bryan,

On Wed, Mar 30, 2011 at 03:31:44PM -0700, Dmitry Torokhov wrote:
> Hi Bryan,
> 
> It is actually one of autofs + NIS, mounts that is failing.
> 

Some more data about NFS problemi I am seeing. With an older kernel I
get:

[dtor@...r-d630 ~]$ sudo mount -v build-toolchain:/toolchain /mnt/
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Thu Mar 31 09:17:38 2011
mount.nfs: trying text-based options 'vers=4,addr=10.17.52.98,clientaddr=10.20.94.47'
mount.nfs: mount(2): Operation not permitted
mount.nfs: trying text-based options 'addr=10.17.52.98'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.17.52.98 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.17.52.98 prog 100005 vers 3 prot UDP port 693
build-toolchain:/toolchain on /mnt type nfs (rw)

The failing kernel does it like this:

[dtor@...r-ws ~]$ sudo mount -v build-toolchain:/toolchain /mnt
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Thu Mar 31 09:14:22 2011
mount.nfs: trying text-based options 'vers=4,addr=10.17.52.98,clientaddr=10.20.94.123'
mount.nfs: mount(2): Resource temporarily unavailable
mount.nfs: Resource temporarily unavailable

And I can mount it successfully if I explicitly request V3:

[dtor@...r-ws ~]$ sudo mount -v -o nfsvers=3 build-toolchain:/toolchain /mnt/
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Thu Mar 31 09:22:57 2011
mount.nfs: trying text-based options 'nfsvers=3,addr=10.17.52.98'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.17.52.98 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.17.52.98 prog 100005 vers 3 prot UDP port 693
build-toolchain:/toolchain on /mnt type nfs (rw,nfsvers=3)

The mounts that succeed automatically with the newer kernel do like
this:

[dtor@...r-ws ~]$ sudo mount -v pa-home:/home2 /mnt/
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Thu Mar 31 09:20:01 2011
mount.nfs: trying text-based options 'vers=4,addr=10.17.4.25,clientaddr=10.20.94.123'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=10.17.4.25'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.17.4.25 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.17.4.25 prog 100005 vers 3 prot UDP port 1234
pa-home:/home2 on /mnt type nfs (rw)

I am not sure why in failing case we are seeing "resource temporarily
unavailable" instead of "protocol not supported".

Thanks.

-- 
Dmitry
--
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/