From: Mike Marshall <hubcap@omnibond.com>
To: colin.king@canonical.com
Cc: Martin Brandenburg <martin@omnibond.com>,
devel@lists.orangefs.org, kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Mike Marshall <hubcap@omnibond.com>
Subject: Re: [PATCH] orangefs: rate limit the client not running info message
Date: Fri, 7 Sep 2018 14:01:48 -0400 [thread overview]
Message-ID: <CAOg9mSTSiqaAiSuxN5uqQWoMF1W5ZXFgZ36jFHOFHRVe7CMraw@mail.gmail.com> (raw)
In-Reply-To: <20180905145401.19772-1-colin.king@canonical.com>
Thanks... I've applied your patch to 4.19-rc2 and run it through xfstests.
It is in my linux-next tree now.
I put that in there because I'm really just an old system administrator,
and I would always be happy when I could tail dmesg and see some
hint at why something wasn't doing as I expected.
I just looked in ratelimit.h and at the ratelimit macros in printk.h,
I should try to think about those more when adding sysadmin-alert
messages.
-Mike
On Wed, Sep 5, 2018 at 10:54 AM Colin King <colin.king@canonical.com> wrote:
>
> From: Colin Ian King <colin.king@canonical.com>
>
> Currently accessing various /sys/fs/orangefs files will spam the
> kernel log with the following info message when the client is not
> running:
>
> [ 491.489284] sysfs_service_op_show: Client not running :-5:
>
> Rate limit this info message to make it less spammy.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> fs/orangefs/orangefs-sysfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/orangefs/orangefs-sysfs.c b/fs/orangefs/orangefs-sysfs.c
> index dd28079f518c..19739aaee675 100644
> --- a/fs/orangefs/orangefs-sysfs.c
> +++ b/fs/orangefs/orangefs-sysfs.c
> @@ -323,7 +323,7 @@ static ssize_t sysfs_service_op_show(struct kobject *kobj,
> /* Can't do a service_operation if the client is not running... */
> rc = is_daemon_in_service();
> if (rc) {
> - pr_info("%s: Client not running :%d:\n",
> + pr_info_ratelimited("%s: Client not running :%d:\n",
> __func__,
> is_daemon_in_service());
> goto out;
> --
> 2.17.1
>
prev parent reply other threads:[~2018-09-07 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 14:54 [PATCH] orangefs: rate limit the client not running info message Colin King
2018-09-07 18:01 ` Mike Marshall [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=CAOg9mSTSiqaAiSuxN5uqQWoMF1W5ZXFgZ36jFHOFHRVe7CMraw@mail.gmail.com \
--to=hubcap@omnibond.com \
--cc=colin.king@canonical.com \
--cc=devel@lists.orangefs.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@omnibond.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).