From: Trond Myklebust <trondmy@hammerspace.com>
To: "bcodding@redhat.com" <bcodding@redhat.com>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: v4 clientid uniquifiers in containers/namespaces
Date: Tue, 8 Feb 2022 16:47:09 +0000 [thread overview]
Message-ID: <573bd3329d0dc2f73986d4c2cf3060c0298ac970.camel@hammerspace.com> (raw)
In-Reply-To: <8CCCD806-A467-432C-B7FF-9E83981533EF@redhat.com>
On Tue, 2022-02-08 at 06:32 -0500, Benjamin Coddington wrote:
>
> There's a bit of a chicken and egg problem with 2, though. If the
> nfs
> module is loaded, the kernel notification gets sent as soon as you
> create
> the namespace. Its not going to wait for you to move or exec udev
> into
> that
> network namespace, and the notification is lost.
Wait a minute... I missed this comment earlier, but it definitely
points to a misunderstanding.
The notification is _not_ sent by the act of loading a module. It is
sent by the call to kobject_uevent() in nfs_netns_sysfs_setup(). That
again is called as part of nfs_net_init() when the net namespace gets
created.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2022-02-08 16:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 15:03 v4 clientid uniquifiers in containers/namespaces Benjamin Coddington
2022-02-05 18:24 ` 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 [this message]
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=573bd3329d0dc2f73986d4c2cf3060c0298ac970.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=bcodding@redhat.com \
--cc=chuck.lever@oracle.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