From: Jeff Layton <jlayton@kernel.org>
To: Vasily Averin <vvs@virtuozzo.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna.schumaker@netapp.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
linux-nfs@vger.kernel.org,
Evgenii Shatokhin <eshatokhin@virtuozzo.com>,
Konstantin Khorenko <khorenko@virtuozzo.com>
Subject: Re: [PATCH 4/4] nfs: fix debug message in svc_create_xprt()
Date: Mon, 17 Dec 2018 12:56:44 -0500 [thread overview]
Message-ID: <285400e54a70548b4404ecdba9e44c4e8e6c5953.camel@kernel.org> (raw)
In-Reply-To: <cff6406f-5c47-d0c6-64c8-48274c811d86@virtuozzo.com>
On Mon, 2018-12-17 at 19:26 +0300, Vasily Averin wrote:
> _svc_create_xprt() returns positive port number
> so its non-zero return value is not an error
>
> Signed-off-by: Vasily Averin <vvs@virtuozzo.com>
> ---
> net/sunrpc/svc_xprt.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/sunrpc/svc_xprt.c b/net/sunrpc/svc_xprt.c
> index 51d36230b6e3..130af22d5c66 100644
> --- a/net/sunrpc/svc_xprt.c
> +++ b/net/sunrpc/svc_xprt.c
> @@ -296,9 +296,9 @@ int svc_create_xprt(struct svc_serv *serv, const char *xprt_name,
> request_module("svc%s", xprt_name);
> err = _svc_create_xprt(serv, xprt_name, net, family, port, flags);
> }
> - if (err)
> + if (err < 0)
> dprintk("svc: transport %s not found, err %d\n",
> - xprt_name, err);
> + xprt_name, -err);
> return err;
> }
> EXPORT_SYMBOL_GPL(svc_create_xprt);
This patch is fine, but _svc_create_xprt does not make it clear that it
returns a positive port number.
Would you be amenable to spinning up a patch to add a kerneldoc comment
over that function (and maybe one over svc_create_xprt too), to make it
clear what it does?
Thanks,
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2018-12-17 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 16:26 [PATCH 4/4] nfs: fix debug message in svc_create_xprt() Vasily Averin
2018-12-17 17:56 ` Jeff Layton [this message]
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=285400e54a70548b4404ecdba9e44c4e8e6c5953.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=eshatokhin@virtuozzo.com \
--cc=khorenko@virtuozzo.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
--cc=vvs@virtuozzo.com \
/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