linux-kernel - recent nfs change causes autofs regression

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]

Message-ID: <000701c7eb49$cff701c0$6fe50540$@com>
Date:	Thu, 30 Aug 2007 14:07:43 -0700
From:	"Hua Zhong" <hzhong@...il.com>
To:	"'Linux Kernel Mailing List'" <linux-kernel@...r.kernel.org>
Cc:	"'Linus Torvalds'" <torvalds@...ux-foundation.org>,
	<akpm@...ux-foundation.org>
Subject: recent nfs change causes autofs regression

I am re-sending this after help from Ian and git-bisect. To me it's a
show-stopper: I cannot find an acceptable workaround that I can implement.

The problem: upgrading to 2.6.23-rc4 from 2.6.22 causes several autofs
mounts to fail silently - they just not appear when they should.

I believe it's caused by the NFS change that forces multiple mounts from
different directories under the same server side filesystem to have the same
mount options by default, otherwise it returns EBUSY.

For example, if server has a filesystem /a, and it exports /a/x and /a/y
(maybe with rw or ro), and a client must mount /a/x and /a/y with the same
mount options now.

Since in my setup they are managed by autofs, and the autofs map is managed
by nis, there is no way I could easily workaround it..

If we have to live with this regression, I want to hear some suggestions
about how to fix them realistically. Thanks.

By the way, I am not sure if I did the bisect right, but FWIW, git-bisect
says:

c98451bdb2f3e6d6cc1e03adad641e9497512b49 is first bad commit
commit c98451bdb2f3e6d6cc1e03adad641e9497512b49
Author: Frank van Maarseveen <frankvm@...nkvm.com>
Date:   Mon Jul 9 22:25:29 2007 +0200

    NLM: fix source address of callback to client

    Use the destination address of the original NLM request as the
    source address in callbacks to the client.

    Signed-off-by: Frank van Maarseveen <frankvm@...nkvm.com>
    Signed-off-by: Trond Myklebust <Trond.Myklebust@...app.com>

:040000 040000 675c84bd8b2c50744018becaa0db4aeca19b8f9f
105fbd3cb3fa5e3019836b4b5268125d0181a72d M      fs
:040000 040000 0138796e0806b4ebd1cc3850ed4e8c7ab24d2d41
2fec08debe51c20423a88b1a0d4281c683ba5daf M      include

-----Original Message-----
From: Hua Zhong [mailto:hzhong@...il.com] 
Sent: Wednesday, August 29, 2007 1:59 PM
To: 'Linux Kernel Mailing List'
Subject: regression of autofs for current git?

Hi,

I am wondering if this is a known issue, but I just built the current git
and several autofs mounts mysteriously disappeared. Restarting autofs could
fix some, but then lose others. 2.6.22 was fine.

Is there anything I could check other than bisect? (It may take some time
for me to get to it)

Thanks for your help.

Hua

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