[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210928154300.GE25415@fieldses.org>
Date: Tue, 28 Sep 2021 11:43:00 -0400
From: "bfields@...ldses.org" <bfields@...ldses.org>
To: Trond Myklebust <trondmy@...merspace.com>
Cc: "neilb@...e.com" <neilb@...e.com>,
"jakub.kicinski@...ronome.com" <jakub.kicinski@...ronome.com>,
"willy@...radead.org" <willy@...radead.org>,
"tyhicks@...onical.com" <tyhicks@...onical.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"wanghai38@...wei.com" <wanghai38@...wei.com>,
"nicolas.dichtel@...nd.com" <nicolas.dichtel@...nd.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"jlayton@...nel.org" <jlayton@...nel.org>,
"ast@...nel.org" <ast@...nel.org>,
"christian.brauner@...ntu.com" <christian.brauner@...ntu.com>,
"chuck.lever@...cle.com" <chuck.lever@...cle.com>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"anna.schumaker@...app.com" <anna.schumaker@...app.com>,
"tom@...pey.com" <tom@...pey.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"cong.wang@...edance.com" <cong.wang@...edance.com>,
"dsahern@...il.com" <dsahern@...il.com>,
"timo@...henpieler.org" <timo@...henpieler.org>,
"jiang.wang@...edance.com" <jiang.wang@...edance.com>,
"kuniyu@...zon.co.jp" <kuniyu@...zon.co.jp>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Rao.Shoaib@...cle.com" <Rao.Shoaib@...cle.com>,
"wenbin.zeng@...il.com" <wenbin.zeng@...il.com>,
"kolga@...app.com" <kolga@...app.com>
Subject: Re: [PATCH net 2/2] auth_gss: Fix deadlock that blocks
rpcsec_gss_exit_net when use-gss-proxy==1
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.
Powered by blists - more mailing lists