Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   "Benjamin Coddington" <bcodding@redhat.com>
To:     "Linux NFS Mailing List" <linux-nfs@vger.kernel.org>
Subject: v4 clientid uniquifiers in containers/namespaces
Date:   Sat, 05 Feb 2022 10:03:46 -0500
Message-ID: <6CEC5101-0512-4082-81F8-BDFEC5B6DF3A@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

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.

I'md interested since it will inform whether I need to send patches to
systemd's udev, and potentially open the can of worms over there.  Yet its
not yet clear to me how an init namespaced udev process can write to a netns
sysfs path.

Another option might be to create yet another daemon/tool that would listen
specifically for these notifications.  Ugh.

Ben