On 7 Feb 2022, at 20:59, NeilBrown wrote: > On Sun, 06 Feb 2022, Benjamin Coddington wrote: >> Hi all, >> >> Is anyone using a udev(-like) implementation with NETLINK_LISTEN_ALL_NSID? >> It looks like that is at least necessary to allow the init namespaced udev >> to receive notifications on /sys/fs/nfs/net/nfs_client/identifier, which >> would be a pre-req to automatically uniquify in containers. > > Could you walk me through the reasoning here - or point me to where it > has been discussed. https://lore.kernel.org/linux-nfs/20210414181040.7108-1-steved@xxxxxxxxxx/ > It seems to me that mount.nfs is the place to set nfs_client/identifier. > It can be told (via /etc/nfs.conf or /etc/nfsmount.conf) how to generate > and where to store the identifier. It can check the current value and > update if needed. As long as the identifier is set before the first > mount, there is no rush. > > Why does it need to be done in response to a uevent?? I think the assertion was that it was the only sensible way, and it does seem to be better than exposing yet another knob when all that's needed is a way to distinguish and persist NFS clients when network namespaces can come and go at any time, and there can be a lot of them. Ben
