public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	Chuck Lever <cel@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>, Neil Brown <neilb@suse.de>,
	Olga Kornievskaia <kolga@netapp.com>,
	Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
	stable@vger.kernel.org, Eirik Fuller <efuller@redhat.com>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfsd: move init of percpu reply_cache_stats counters back to nfsd_init_net
Date: Sun, 18 Jun 2023 08:09:50 -0400	[thread overview]
Message-ID: <7d9515dbe6af110f2c32dce2b994120e4637b295.camel@kernel.org> (raw)
In-Reply-To: <d698b838-57e0-d019-a783-c229c04eeca4@leemhuis.info>

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. The original patch
description didn't point out how easy it is to trigger a panic with
this, so I was hoping to convince him.

To further that argument too:

I have to wonder if this bug might cause (temporary?) memory corruption
on x86_64. The code hits a spinlock in that struct, so there may be a
window of time where it doesn't contain what's expected.

> > > > Cc: stable@vger.kernel.org # v6.3+
> > > > Fixes: f5f9d4a314da ("nfsd: move reply cache initialization into nfsd startup")
> > > 
> > > Why both Fixes: and Cc: stable?
> > 
> > *shrug* : they mean different things. I can drop the Cc stable.
> 
> Please leave it, only a stable tag ensures backporting; a fixes tag
> alone is not enough. See [1] above or these recent messages from Greg:
> 
> https://lore.kernel.org/all/2023061137-algorithm-almanac-1337@gregkh/
> https://lore.kernel.org/all/2023060703-colony-shakily-3514@gregkh/
> 

Chuck and I also recently requested that the stable series not pick
patches automatically for fs/nfsd. This does need to be backported
though, so I cc'ed stable to make that clear.
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2023-06-18 12:10 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 [this message]
2023-06-18 14:02         ` Thorsten Leemhuis
2023-06-18 15:59         ` Chuck Lever III
2023-06-19 11:03           ` Jeff Layton

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=7d9515dbe6af110f2c32dce2b994120e4637b295.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=cel@kernel.org \
    --cc=chuck.lever@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