From: Benjamin Coddington <bcodding@redhat.com>
To: trondmy@kernel.org
Cc: linux-nfs@vger.kernel.org, Jeff Layton <jlayton@kernel.org>,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH v3 1/6] SUNRPC: rpcbind should never reset the port to the value '0'
Date: Wed, 26 Mar 2025 06:43:17 -0400 [thread overview]
Message-ID: <6161CDDF-5922-4BB1-903E-C00A8B48AA40@redhat.com> (raw)
In-Reply-To: <b8af12ef4fb9b3f0a3b22b23d13c573df3367ee8.1742941932.git.trond.myklebust@hammerspace.com>
On 25 Mar 2025, at 18:35, trondmy@kernel.org wrote:
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
>
> If we already had a valid port number for the RPC service, then we
> should not allow the rpcbind client to set it to the invalid value '0'.
>
> Reviewed-by: Jeff Layton <jlayton@kernel.org>
> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
> ---
> net/sunrpc/rpcb_clnt.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/net/sunrpc/rpcb_clnt.c b/net/sunrpc/rpcb_clnt.c
> index 102c3818bc54..53bcca365fb1 100644
> --- a/net/sunrpc/rpcb_clnt.c
> +++ b/net/sunrpc/rpcb_clnt.c
> @@ -820,9 +820,10 @@ static void rpcb_getport_done(struct rpc_task *child, void *data)
> }
>
> trace_rpcb_setport(child, map->r_status, map->r_port);
> - xprt->ops->set_port(xprt, map->r_port);
> - if (map->r_port)
> + if (map->r_port) {
> + xprt->ops->set_port(xprt, map->r_port);
> xprt_set_bound(xprt);
> + }
> }
>
> /*
> --
> 2.49.0
Reviewed-by: Benjamin Coddington <bcodding@redhat.com>
Ben
next prev parent reply other threads:[~2025-03-26 10:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 22:35 [PATCH v3 0/6] Ensure that ENETUNREACH terminates state recovery trondmy
2025-03-25 22:35 ` [PATCH v3 1/6] SUNRPC: rpcbind should never reset the port to the value '0' trondmy
2025-03-26 10:43 ` Benjamin Coddington [this message]
2025-03-25 22:35 ` [PATCH v3 2/6] SUNRPC: rpc_clnt_set_transport() must not change the autobind setting trondmy
2025-03-26 10:43 ` Benjamin Coddington
2025-03-25 22:35 ` [PATCH v3 3/6] NFS: Shut down the nfs_client only after all the superblocks trondmy
2025-03-26 0:15 ` Jeff Layton
2025-03-26 0:37 ` Trond Myklebust
2025-03-26 10:07 ` Benjamin Coddington
2025-03-25 22:35 ` [PATCH v3 4/6] NFSv4: Further cleanups to shutdown loops trondmy
2025-03-26 0:17 ` Jeff Layton
2025-03-26 10:13 ` Jeff Layton
2025-03-26 10:46 ` Benjamin Coddington
2025-03-26 18:11 ` Trond Myklebust
2025-03-26 18:21 ` Jeff Layton
2025-03-26 18:24 ` Trond Myklebust
2025-03-27 0:35 ` Jeff Layton
2025-03-25 22:35 ` [PATCH v3 5/6] NFSv4: clp->cl_cons_state < 0 signifies an invalid nfs_client trondmy
2025-03-26 0:17 ` Jeff Layton
2025-03-26 10:46 ` Benjamin Coddington
2025-03-25 22:35 ` [PATCH v3 6/6] NFSv4: Treat ENETUNREACH errors as fatal for state recovery trondmy
2025-03-26 10:39 ` Benjamin Coddington
2025-03-26 11:18 ` Jeff Layton
2025-03-26 13:10 ` 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=6161CDDF-5922-4BB1-903E-C00A8B48AA40@redhat.com \
--to=bcodding@redhat.com \
--cc=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