Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
From:   "NeilBrown" <neilb@suse.de>
To:     "Petr Vorel" <pvorel@suse.cz>
Cc:     linux-nfs@vger.kernel.org,
        "J. Bruce Fields" <bfields@fieldses.org>,
        "Chuck Lever" <chuck.lever@oracle.com>,
        "Trond Myklebust" <trond.myklebust@hammerspace.com>,
        "Anna Schumaker" <anna.schumaker@netapp.com>,
        "Steve Dickson" <SteveD@redhat.com>,
        "Nikita Yushchenko" <nikita.yushchenko@virtuozzo.com>,
        ltp@lists.linux.it
Subject: Re: LTP nfslock01 test failing on NFS v3 (lockd: cannot monitor 10.0.0.2)
In-reply-to: <YebcNQg0u5cU1QyQ@pevik>
References: <YebcNQg0u5cU1QyQ@pevik>
Date:   Wed, 19 Jan 2022 09:11:57 +1100
Message-id: <164254391708.24166.6930987548904227011@noble.neil.brown.name>
Precedence: bulk

On Wed, 19 Jan 2022, Petr Vorel wrote:
> Hi all,
>=20
> this is a test failure posted by Nikita Yushchenko [1]. LTP NFS test nfsloc=
k01
> looks to be failing on NFS v3:
>=20
> "not unsharing /var makes AF_UNIX socket for host's rpcbind to become avail=
able
> inside ltpns. Then, at nfs3 mount time, kernel creates an instance of lockd=
 for
> ltpns, and ports for that instance leak to host's rpcbind and overwrite por=
ts
> for lockd already active for root namespace. This breaks nfs3 file locking."

"not unsharing /var" ....  can this be fixed by simply unsharing /var?
Or is that not simple?

On could easily argue that RPCBIND_SOCK_PATHNAME in the kernel should be
changed to "/run/rpcbind.sock".  Does this test suite unshare /run ??

BTW, your email contains [1], [2], etc which suggests there are links
somewhere - but there aren't.

NeilBrown