From: Steve Dickson <SteveD@redhat.com>
To: Mi Jinlong <mijinlong@cn.fujitsu.com>
Cc: NFS <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Gssd: modify wrong err message at handle_gssd_upcall
Date: Wed, 09 Feb 2011 11:34:47 -0500 [thread overview]
Message-ID: <4D52C227.7050007@RedHat.com> (raw)
In-Reply-To: <4D523618.8080106@cn.fujitsu.com>
On 02/09/2011 01:37 AM, Mi Jinlong wrote:
> Modify wrong err message at handle_gssd_upcall when
> sscanf encryption types fail.
>
> Signed-off-by: Mi Jinlong <mijinlong@cn.fujitsu.com>
> ---
> utils/gssd/gssd_proc.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/utils/gssd/gssd_proc.c b/utils/gssd/gssd_proc.c
> index c301d46..41328c9 100644
> --- a/utils/gssd/gssd_proc.c
> +++ b/utils/gssd/gssd_proc.c
> @@ -1245,7 +1245,7 @@ handle_gssd_upcall(struct clnt_info *clp)
> goto out;
> if (sscanf(p, "enctypes=%s", enctypes) != 1) {
> printerr(0, "WARNING: handle_gssd_upcall: "
> - "failed to parse target name "
> + "failed to parse encryption types "
> "in upcall string '%s'\n", lbuf);
> goto out;
> }
Committed...
steved.
prev parent reply other threads:[~2011-02-09 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 6:37 [PATCH] Gssd: modify wrong err message at handle_gssd_upcall Mi Jinlong
2011-02-09 16:34 ` Steve Dickson [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=4D52C227.7050007@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=mijinlong@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).