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 [thread overview]
Message-ID: <6CEC5101-0512-4082-81F8-BDFEC5B6DF3A@redhat.com> (raw)
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
next reply other threads:[~2022-02-05 15:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 15:03 Benjamin Coddington [this message]
2022-02-05 18:24 ` v4 clientid uniquifiers in containers/namespaces Trond Myklebust
2022-02-05 19:50 ` Benjamin Coddington
2022-02-07 14:05 ` Benjamin Coddington
2022-02-07 15:49 ` Chuck Lever III
2022-02-07 19:38 ` Trond Myklebust
2022-02-07 23:59 ` Chuck Lever III
2022-02-08 11:32 ` Benjamin Coddington
2022-02-08 13:45 ` Trond Myklebust
2022-02-08 14:29 ` Benjamin Coddington
2022-02-08 14:42 ` Chuck Lever III
2022-02-08 15:23 ` Benjamin Coddington
2022-02-08 15:43 ` Trond Myklebust
2022-02-08 15:47 ` Trond Myklebust
2022-02-08 16:18 ` Benjamin Coddington
2022-02-08 16:47 ` Trond Myklebust
2022-02-08 17:45 ` Benjamin Coddington
2022-02-08 1:59 ` NeilBrown
2022-02-08 11:52 ` Benjamin Coddington
2022-02-08 20:56 ` NeilBrown
2022-02-08 23:34 ` Trond Myklebust
2022-02-09 1:24 ` NeilBrown
2022-02-15 16:57 ` Benjamin Coddington
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6CEC5101-0512-4082-81F8-BDFEC5B6DF3A@redhat.com \
--to=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox