From: "J. Bruce Fields" <bfields@fieldses.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd: don't WARN/backtrace for invalid container deployment.
Date: Tue, 25 Aug 2015 17:16:18 -0400 [thread overview]
Message-ID: <20150825211618.GE8579@fieldses.org> (raw)
In-Reply-To: <20150825210642.GG3560@windriver.com>
On Tue, Aug 25, 2015 at 05:06:43PM -0400, Paul Gortmaker wrote:
> [[PATCH] nfsd: don't WARN/backtrace for invalid container deployment.] On 25/08/2015 (Tue 16:59) Paul Gortmaker wrote:
>
> > These messages, combined with the backtrace they trigger, makes it seem
> > like a serious problem, though a quick search shows distros marking
> > it as a "won't fix" non-issue when the problem is reported by users.
>
> Ah crap, didn't notice I was on a slightly older kernel when generating
> this ; it still applies to master with minor fuzz. I can resend if need
> be, and if folks are OK with the general approach.
Well, this really is something we need to fix, but given that it's going
to take a while, OK, maybe toning this down is best.
--b.
>
> Paul.
> --
>
> >
> > The backtrace is overkill, and only really manages to show that if
> > you follow the code path, you can't really avoid it with bootargs
> > or configuration settings in the container.
> >
> > Given that, lets tone it down a bit and get rid of the WARN severity,
> > and the associated backtrace, so people aren't needlessly alarmed.
> >
> > Also, lets drop the split printk line, since they are grep unfriendly.
> >
> > Cc: "J. Bruce Fields" <bfields@fieldses.org>
> > Cc: linux-nfs@vger.kernel.org
> > Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> >
> > diff --git a/fs/nfsd/nfs4recover.c b/fs/nfsd/nfs4recover.c
> > index 9c271f42604a..fe8a3da5eb63 100644
> > --- a/fs/nfsd/nfs4recover.c
> > +++ b/fs/nfsd/nfs4recover.c
> > @@ -526,8 +526,7 @@ nfsd4_legacy_tracking_init(struct net *net)
> >
> > /* XXX: The legacy code won't work in a container */
> > if (net != &init_net) {
> > - WARN(1, KERN_ERR "NFSD: attempt to initialize legacy client "
> > - "tracking in a container!\n");
> > + pr_warn("NFSD: attempt to initialize legacy client tracking in a container ignored.\n");
> > return -EINVAL;
> > }
> >
> > @@ -1191,8 +1190,7 @@ nfsd4_umh_cltrack_init(struct net __attribute__((unused)) *net)
> > {
> > /* XXX: The usermode helper s not working in container yet. */
> > if (net != &init_net) {
> > - WARN(1, KERN_ERR "NFSD: attempt to initialize umh client "
> > - "tracking in a container!\n");
> > + pr_warn("NFSD: attempt to initialize umh client tracking in a container ignored.\n");
> > return -EINVAL;
> > }
> > return nfsd4_umh_cltrack_upcall("init", NULL, NULL);
> > --
> > 2.1.0
> >
next prev parent reply other threads:[~2015-08-25 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 20:59 [PATCH] nfsd: don't WARN/backtrace for invalid container deployment Paul Gortmaker
2015-08-25 21:06 ` Paul Gortmaker
2015-08-25 21:16 ` J. Bruce Fields [this message]
2015-08-26 19:07 ` J. Bruce Fields
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=20150825211618.GE8579@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=paul.gortmaker@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.