From: Jeff Layton <jlayton@kernel.org>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
Gregory Farnum <gfarnum@redhat.com>,
Luis Henriques <lhenriques@suse.com>
Subject: Re: [PATCH] ceph: demote quotarealm lookup warning to a debug message
Date: Thu, 07 May 2020 09:44:13 -0400 [thread overview]
Message-ID: <e5839bffe4939c6290d74ca2fb39310bd4916c16.camel@kernel.org> (raw)
In-Reply-To: <20200505125902.GA10381@suse.com>
On Tue, 2020-05-05 at 13:59 +0100, Luis Henriques wrote:
> A misconfigured cephx can easily result in having the kernel client
> flooding the logs with:
>
> ceph: Can't lookup inode 1 (err: -13)
>
> Change his message to debug level.
>
> Link: https://tracker.ceph.com/issues/44546
> Signed-off-by: Luis Henriques <lhenriques@suse.com>
> ---
> Hi!
>
> This patch should fix some harmless warnings when using cephx to restrict
> users access to certain filesystem paths. I've added a comment to the
> tracker where removing this warning could result (unlikely, IMHO!) in an
> admin to miss not-so-harmless bogus configurations.
>
> Cheers,
> --
> Luís
>
> fs/ceph/quota.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ceph/quota.c b/fs/ceph/quota.c
> index de56dee60540..19507e2fdb57 100644
> --- a/fs/ceph/quota.c
> +++ b/fs/ceph/quota.c
> @@ -159,8 +159,8 @@ static struct inode *lookup_quotarealm_inode(struct ceph_mds_client *mdsc,
> }
>
> if (IS_ERR(in)) {
> - pr_warn("Can't lookup inode %llx (err: %ld)\n",
> - realm->ino, PTR_ERR(in));
> + dout("Can't lookup inode %llx (err: %ld)\n",
> + realm->ino, PTR_ERR(in));
> qri->timeout = jiffies + msecs_to_jiffies(60 * 1000); /* XXX */
> } else {
> qri->timeout = 0;
>
Ilya,
We've had a number of reports where people get a ton of kernel log spam
when they hit this problem. I think we probably ought to mark this patch
for stable and go ahead and send it to Linus for v5.7 -- any objection?
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2020-05-07 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 12:59 [PATCH] ceph: demote quotarealm lookup warning to a debug message Luis Henriques
2020-05-05 14:55 ` Jeff Layton
2020-05-07 13:44 ` Jeff Layton [this message]
2020-05-07 16:26 ` Ilya Dryomov
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=e5839bffe4939c6290d74ca2fb39310bd4916c16.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=gfarnum@redhat.com \
--cc=idryomov@gmail.com \
--cc=lhenriques@suse.com \
--cc=linux-kernel@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