From: Chuck Lever <chuck.lever@oracle.com>
To: kazuo ito <kzpn200@gmail.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org, Jeff Layton <jlayton@kernel.org>
Subject: Re: [PATCH] nfsd: Fix message level for normal termination
Date: Thu, 26 Nov 2020 22:56:21 -0500 [thread overview]
Message-ID: <7BA358F0-01C3-4530-B5EE-1CBBCE3843C2@oracle.com> (raw)
In-Reply-To: <20201127024439.32297-1-kzpn200@gmail.com>
> On Nov 26, 2020, at 9:46 PM, kazuo ito <kzpn200@gmail.com> wrote:
>
> A warning message from nfsd terminating normally
> can confuse system adminstrators or monitoring software.
>
> Though it's not exactly fair to pin-point a commit where it
> originated, the current form in the current place started
> to appear in:
>
> Fixes: e096bbc6488d ("knfsd: remove special handling for SIGHUP")
> Signed-off-by: kazuo ito <kzpn200@gmail.com>
> ---
> fs/nfsd/nfssvc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
> index f7f6473578af..b08cccb71787 100644
> --- a/fs/nfsd/nfssvc.c
> +++ b/fs/nfsd/nfssvc.c
> @@ -527,8 +527,8 @@ static void nfsd_last_thread(struct svc_serv *serv, struct net *net)
> return;
>
> nfsd_shutdown_net(net);
> - printk(KERN_WARNING "nfsd: last server has exited, flushing export "
> - "cache\n");
> + printk(KERN_INFO "nfsd: last server has exited, flushing export "
> + "cache\n");
pr_info(), please! And see if it will fit on one line.
> nfsd_export_flush(net);
> }
>
> --
> 2.20.1
>
next prev parent reply other threads:[~2020-11-27 3:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 2:44 [PATCH] nfsd: Fix message level for normal termination kazuo ito
2020-11-27 3:56 ` Chuck Lever [this message]
2020-11-27 6:26 ` kazuo ito
2020-11-27 17:11 ` Chuck Lever
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=7BA358F0-01C3-4530-B5EE-1CBBCE3843C2@oracle.com \
--to=chuck.lever@oracle.com \
--cc=bfields@fieldses.org \
--cc=jlayton@kernel.org \
--cc=kzpn200@gmail.com \
--cc=linux-nfs@vger.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