Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: trondmy@kernel.org, linux-nfs@vger.kernel.org
Cc: Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH v2 2/4] SUNRPC: rpc_clnt_set_transport() must not change the autobind setting
Date: Tue, 25 Mar 2025 13:55:59 -0400	[thread overview]
Message-ID: <25680d0e03c82061f9662473f6c7767449e21e1a.camel@kernel.org> (raw)
In-Reply-To: <f6c87857690a66e7f1ee684c755f6c97d8913d64.1742919341.git.trond.myklebust@hammerspace.com>

On Tue, 2025-03-25 at 12:17 -0400, trondmy@kernel.org wrote:
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
> 
> The autobind setting was supposed to be determined in rpc_create(),
> since commit c2866763b402 ("SUNRPC: use sockaddr + size when creating
> remote transport endpoints").
> 

Should this have:

    Fixes: c2866763b402 ("SUNRPC: use sockaddr + size when creating remote transport endpoints")

?

Though I guess that commit is old enough that maybe it doesn't matter.

> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
> ---
>  net/sunrpc/clnt.c | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/net/sunrpc/clnt.c b/net/sunrpc/clnt.c
> index 1cfaf93ceec1..6f75862d9782 100644
> --- a/net/sunrpc/clnt.c
> +++ b/net/sunrpc/clnt.c
> @@ -270,9 +270,6 @@ static struct rpc_xprt *rpc_clnt_set_transport(struct rpc_clnt *clnt,
>  	old = rcu_dereference_protected(clnt->cl_xprt,
>  			lockdep_is_held(&clnt->cl_lock));
>  
> -	if (!xprt_bound(xprt))
> -		clnt->cl_autobind = 1;
> -
>  	clnt->cl_timeout = timeout;
>  	rcu_assign_pointer(clnt->cl_xprt, xprt);
>  	spin_unlock(&clnt->cl_lock);

Reviewed-by: Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2025-03-25 17:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 16:17 [PATCH v2 0/4] Ensure that ENETUNREACH terminates state recovery trondmy
2025-03-25 16:17 ` [PATCH v2 1/4] SUNRPC: rpcbind should never reset the port to the value '0' trondmy
2025-03-25 17:56   ` Jeff Layton
2025-03-25 16:17 ` [PATCH v2 2/4] SUNRPC: rpc_clnt_set_transport() must not change the autobind setting trondmy
2025-03-25 17:55   ` Jeff Layton [this message]
2025-03-25 16:17 ` [PATCH v2 3/4] NFSv4: clp->cl_cons_state < 0 signifies an invalid nfs_client trondmy
2025-03-25 17:59   ` Jeff Layton
2025-03-25 18:48     ` Trond Myklebust
2025-03-25 19:44       ` Jeff Layton
2025-03-25 20:30         ` Trond Myklebust
2025-03-25 16:17 ` [PATCH v2 4/4] NFSv4: Treat ENETUNREACH errors as fatal for state recovery trondmy
2025-03-25 18:04   ` Jeff Layton
2025-03-25 18:50     ` Trond Myklebust
2025-03-25 19:26       ` Jeff Layton
2025-03-25 19:40 ` Concerns about ENETUNREACH patch series Re: [PATCH v2 0/4] Ensure that ENETUNREACH terminates " Lionel Cons
2025-03-25 20:42   ` Trond Myklebust

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=25680d0e03c82061f9662473f6c7767449e21e1a.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-nfs@vger.kernel.org \
    --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