From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D4DC84071DA; Fri, 5 Jun 2026 22:07:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780697237; cv=none; b=XjmuwP3KNMTgokTVsqO2JTb95fUhrnmKdlg+NYcBlSaDheJun5YEKb1edDcHVIYCpR4waCBT1h6dcUrQgcnnHSYuKI86ULqvPc9Ww/xaPUI5UT1H7mWGZa0E0TSFCR4ToG65DNcOU30HoUFJauDulnNVsb0PX5BoRAdlsSRejBQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780697237; c=relaxed/simple; bh=Y7Pg5fAh9/b5hmp7rfWDWVRBVVLAi2cd9RJLnka7Lmg=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=grvAhH5mE2LSZxsEuX3jiJtLJ6rL8zqGu4EBxbzYzDIhO8FE2DucY2qdXDgxu6+HSH5vucDA97kgPdIESX9WKXGudq1inqKUYVxAZw/b4JfM8yLkKY8g4Vk3dxkIcxkF7EA2DrYBORr9TxjaeFSyN6dATKGdceLJV2RJbtbYawg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=MeIsVr4j; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="MeIsVr4j" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 20AC51F00893; Fri, 5 Jun 2026 22:07:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1780697236; bh=m+mXMDeY7i9LI/iEgBGFnHjF6kqWb3xtVcPntuQ526Y=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=MeIsVr4j5hVwn6+MWIlSgN5x+LeQ3FeifCYJV3/xzXIvAek4ekcjeIttlWgtypGwh WD9G2G15LSZGB+oz6EcWuyrxi0CgbxufwBGgHs9lJ+yTEhqjeRjdYyaW8nNDus4VTI Wkb6i5MobgWKxdRn90Z6z9mFJySR24kGLSFmyLyWw6ruvFh1r5qgeZkO8kIwsFw+0R LfsfUiGJ0y/qTLo1It1aA4y45X4jX+ccUZY5HtbuJdaigpu28nzE5vbnYrkc/BeIDU Lb56gcbugE7qG70YKNJhjPpHaWBEYzHSfEQYlAqlCiWrQEwaCS5LRpSFxIKYI1KfgO t8Isa/Z1g5MUA== Message-ID: Date: Fri, 5 Jun 2026 15:07:15 -0700 Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC] NFS: named client identities for mTLS mounts and a per-namespace .nfs keyring To: Sagi Grimberg , Hannes Reinecke , linux-nfs@vger.kernel.org Cc: keyrings@vger.kernel.org, kernel-tls-handshake@lists.linux.dev, netdev@vger.kernel.org, Trond Myklebust , Anna Schumaker , Christoph Hellwig , David Howells , Jarkko Sakkinen References: <20260602154740.49861-1-cel@kernel.org> From: Chuck Lever Content-Language: en-US Organization: kernel.org In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 6/5/26 2:32 PM, Sagi Grimberg wrote: > > > On 03/06/2026 17:27, Chuck Lever wrote: >> On Tue, Jun 2, 2026, at 6:39 PM, Hannes Reinecke wrote: >>> I am all for making keyrings namespace-aware. Logically I _think_ they >>> should be tagged per user-namespace, as this really is about the >>> filesystem (and as such would warrant to be tagged per mount ns). >>> Tagging it per net-namespace is not a great fit (well, for me, at >>> least), as also block devices might require keys to present the >>> bdev (eg nvme authentication) >> My understanding of the proposal is that there is one keyring on the >> system for .nfs and the keys in it are visible only in the namespace >> where they were created. >> >> Therefore the consumer (say, NFS, or NFSD) is running in a particular >> network namespace. It will create keys on the one .nfs keyring, but >> only the tlshd in that same network namespace will have access to >> those keys. > > Can tlshd run in multiple network namesapces today? AIUI the netlink upcall in the kernel wants to use a netlink socket in the current network namespace. So there has to be at least one tlshd instance in each network namespace that wants to use in-kernel TLS consumers. -- Chuck Lever