Hi Neil, all, > On Wed, 19 Jan 2022, Petr Vorel wrote: > > Hi all, > > this is a test failure posted by Nikita Yushchenko [1]. LTP NFS test nfslock01 > > looks to be failing on NFS v3: > > "not unsharing /var makes AF_UNIX socket for host's rpcbind to become available > > 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 ports > > 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. I'm sorry, here they are: [1] https://lore.kernel.org/ltp/590378ee-71af-deb6-6c03-1d2af459ed63@xxxxxxxxxxxxx/ (the report) [2] https://lore.kernel.org/ltp/20220112161942.4065665-1-nikita.yushchenko@xxxxxxxxxxxxx/ (the not yet merged LTP Nikita's patch) [3] https://github.com/pevik/ltp/commits/nfs_flock/fail-on-error (my LTP fork with Nikita's patch [2] + strace debugging - with this code I post the report) Kind regards, Petr > NeilBrown
