Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: Trond Myklebust <trondmy@kernel.org>,
	Anna Schumaker <anna@kernel.org>,
	 Omar Sandoval <osandov@osandov.com>,
	Sargun Dillon <sargun@sargun.me>,
	linux-nfs@vger.kernel.org, 	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] nfs: don't share pNFS DS connections between net namespaces
Date: Fri, 11 Apr 2025 10:10:40 -0400	[thread overview]
Message-ID: <c81c2e8cc891bc07ed81eb5e89a3951aa77d3bdc.camel@kernel.org> (raw)
In-Reply-To: <1587C44B-7BDE-4B36-8CE6-C654CB154228@redhat.com>

On Fri, 2025-04-11 at 09:57 -0400, Benjamin Coddington wrote:
> On 10 Apr 2025, at 16:42, Jeff Layton wrote:
> 
> > Currently, different NFS clients can share the same DS connections, even
> > when they are in different net namespaces. If a containerized client
> > creates a DS connection, another container can find and use it. When the
> > first client exits, the connection will which can lead to stalls in
> 
>                                          ^^ close ?
> 

Yes, thanks. Trond/Anna, can you fix before merging?

> > other clients.
> > 
> > Add a net namespace pointer to struct nfs4_pnfs_ds, and compare those
> > value to the caller's netns in _data_server_lookup_locked() when
> > searching for a nfs4_pnfs_ds to match.
> > 
> > Reported-by: Omar Sandoval <osandov@osandov.com>
> > Reported-by: Sargun Dillon <sargun@sargun.me>
> > Closes: https://lore.kernel.org/linux-nfs/Z_ArpQC_vREh_hEA@telecaster/
> > Tested-by: Sargun Dillon <sargun@sargun.me>
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> 
> Looks good to me,
> 
> Reviewed-by: Benjamin Coddington <bcodding@redhat.com>
> 
> Ben
> 

Thank you!
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2025-04-11 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 20:42 [PATCH v2 0/2] nfs: don't share pNFS DS connections between net namespaces Jeff Layton
2025-04-10 20:42 ` [PATCH v2 1/2] " Jeff Layton
2025-04-11 13:57   ` Benjamin Coddington
2025-04-11 14:10     ` Jeff Layton [this message]
2025-04-10 20:42 ` [PATCH v2 2/2] nfs: move the nfs4_data_server_cache into struct nfs_net Jeff Layton
2025-04-11 14:08   ` Benjamin Coddington
2025-04-21 13:30 ` [PATCH v2 0/2] nfs: don't share pNFS DS connections between net namespaces Jeff Layton

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=c81c2e8cc891bc07ed81eb5e89a3951aa77d3bdc.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=anna@kernel.org \
    --cc=bcodding@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=osandov@osandov.com \
    --cc=sargun@sargun.me \
    --cc=trondmy@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