From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "neilb@suse.com" <neilb@suse.com>,
"jakub.kicinski@netronome.com" <jakub.kicinski@netronome.com>,
"willy@infradead.org" <willy@infradead.org>,
"tyhicks@canonical.com" <tyhicks@canonical.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"wanghai38@huawei.com" <wanghai38@huawei.com>,
"nicolas.dichtel@6wind.com" <nicolas.dichtel@6wind.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"ast@kernel.org" <ast@kernel.org>,
"christian.brauner@ubuntu.com" <christian.brauner@ubuntu.com>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>,
"tom@talpey.com" <tom@talpey.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"cong.wang@bytedance.com" <cong.wang@bytedance.com>,
"dsahern@gmail.com" <dsahern@gmail.com>,
"timo@rothenpieler.org" <timo@rothenpieler.org>,
"jiang.wang@bytedance.com" <jiang.wang@bytedance.com>,
"kuniyu@amazon.co.jp" <kuniyu@amazon.co.jp>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Rao.Shoaib@oracle.com" <Rao.Shoaib@oracle.com>,
"wenbin.zeng@gmail.com" <wenbin.zeng@gmail.com>,
"kolga@netapp.com" <kolga@netapp.com>
Subject: Re: [PATCH net 2/2] auth_gss: Fix deadlock that blocks rpcsec_gss_exit_net when use-gss-proxy==1
Date: Tue, 28 Sep 2021 11:43:00 -0400 [thread overview]
Message-ID: <20210928154300.GE25415@fieldses.org> (raw)
In-Reply-To: <8b0e774bdb534c69b0612103acbe61c628fde9b1.camel@hammerspace.com>
On Tue, Sep 28, 2021 at 03:36:58PM +0000, Trond Myklebust wrote:
> What is the use case here? Starting the gssd daemon or knfsd in
> separate chrooted environments? We already know that they have to be
> started in the same net namespace, which pretty much ensures it has to
> be the same container.
Somehow I forgot that knfsd startup is happening in some real process's
context too (not just a kthread).
OK, great, I agree, that sounds like it should work.
--b.
next prev parent reply other threads:[~2021-09-28 15:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 3:14 [PATCH net 0/2] auth_gss: Fix netns refcount leaks when use-gss-proxy==1 Wang Hai
2021-09-28 3:14 ` [PATCH net 1/2] net: Modify unix_stream_connect to not reference count the netns of kernel sockets Wang Hai
2021-09-28 12:50 ` Kuniyuki Iwashima
2021-09-28 3:14 ` [PATCH net 2/2] auth_gss: Fix deadlock that blocks rpcsec_gss_exit_net when use-gss-proxy==1 Wang Hai
2021-09-28 13:30 ` Trond Myklebust
2021-09-28 13:49 ` bfields
2021-09-28 14:04 ` Trond Myklebust
2021-09-28 14:17 ` bfields
2021-09-28 14:27 ` Trond Myklebust
2021-09-28 14:57 ` bfields
2021-09-28 15:36 ` Trond Myklebust
2021-09-28 15:43 ` bfields [this message]
2021-09-29 21:12 ` bfields
2021-09-30 1:56 ` wanghai (M)
2021-11-09 17:21 ` bfields
2021-11-17 19:19 ` bfields
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=20210928154300.GE25415@fieldses.org \
--to=bfields@fieldses.org \
--cc=Rao.Shoaib@oracle.com \
--cc=anna.schumaker@netapp.com \
--cc=ast@kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=chuck.lever@oracle.com \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiang.wang@bytedance.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=timo@rothenpieler.org \
--cc=tom@talpey.com \
--cc=trondmy@hammerspace.com \
--cc=tyhicks@canonical.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wanghai38@huawei.com \
--cc=wenbin.zeng@gmail.com \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.