From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever III <chuck.lever@oracle.com>,
Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Chuck Lever <cel@kernel.org>, Neil Brown <neilb@suse.de>,
Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
linux-stable <stable@vger.kernel.org>,
Eirik Fuller <efuller@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nfsd: move init of percpu reply_cache_stats counters back to nfsd_init_net
Date: Mon, 19 Jun 2023 07:03:27 -0400 [thread overview]
Message-ID: <356b94ef10dc12063da5dc145b61a47ddff5c23a.camel@kernel.org> (raw)
In-Reply-To: <9154BA25-C795-4BEF-B32D-EAB8679E9472@oracle.com>
On Sun, 2023-06-18 at 15:59 +0000, Chuck Lever III wrote:
>
> > On Jun 18, 2023, at 8:09 AM, Jeff Layton <jlayton@kernel.org> wrote:
> >
> > On Sun, 2023-06-18 at 12:40 +0200, Thorsten Leemhuis wrote:
> > > On 16.06.23 22:54, Jeff Layton wrote:
> > > > On Fri, 2023-06-16 at 16:27 -0400, Chuck Lever wrote:
> > > > > Thanks Eirik and Jeff.
> > > > >
> > > > > At this point in the release cycle, I plan to apply this for the
> > > > > next merge window (6.5).
> > > >
> > > > I think we should take this in sooner. This is a regression and a
> > > > user-triggerable oops in the right situation. If:
> > > >
> > > > - non-x86_64 arch
> > > > - /proc/fs/nfsd is mounted in the namespace
> > > > - nfsd is not started in the namespace
> > > > - unprivileged user calls "cat /proc/fs/nfsd/reply_cache_stats"
> > >
> > > FWIW, might be worth to simply tell Linus about it and let him decide,
> > > that's totally fine and even documented in the old and the new docs for
> > > handling regressions[1].
> > >
> > > [1]
> > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/Documentation/process/handling-regressions.rst?id=eed892da9cd08be76a8f467c600ef58716dbb4d2
> > >
> >
> > I'd rather Chuck make the final call here.
>
> Thanks! I feel this one needs broader testing than we can manage
> in just a couple of days. If this were earlier in the -rc cycle
> I would pull the patch right into 6.4-rc without hesitation. It
> is obviously -rc material, but the timing is unfortunate.
>
> I'm planning the nfsd for-6.5 pull request early in the merge
> window, so practically speaking it shouldn't delay the finalized
> upstream version of this patch by more than a few days.
>
>
Ok. I'll trust your judgment then and just cultivate my patience!
Cheers,
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2023-06-19 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 19:17 [PATCH] nfsd: move init of percpu reply_cache_stats counters back to nfsd_init_net Jeff Layton
2023-06-16 20:27 ` Chuck Lever
2023-06-16 20:54 ` Jeff Layton
2023-06-18 10:40 ` Thorsten Leemhuis
2023-06-18 12:09 ` Jeff Layton
2023-06-18 14:02 ` Thorsten Leemhuis
2023-06-18 15:59 ` Chuck Lever III
2023-06-19 11:03 ` Jeff Layton [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=356b94ef10dc12063da5dc145b61a47ddff5c23a.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=efuller@redhat.com \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=regressions@leemhuis.info \
--cc=stable@vger.kernel.org \
--cc=tom@talpey.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