From: Andrew Morton <akpm@linux-foundation.org>
To: Hui Su <sh_def@163.com>
Cc: ryabinin.a.a@gmail.com, glider@google.com, andreyknvl@gmail.com,
dvyukov@google.com, vincenzo.frascino@arm.com,
qiang1.zhang@intel.com, kasan-dev@googlegroups.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] kasan: fix cache shrink race with CPU hotplug
Date: Fri, 7 Aug 2026 14:38:04 -0700 [thread overview]
Message-ID: <20260807143804.24cfd5710208d9a421b0e0e1@linux-foundation.org> (raw)
In-Reply-To: <20260807065038.2600949-1-sh_def@163.com>
On Fri, 7 Aug 2026 14:50:31 +0800 Hui Su <sh_def@163.com> wrote:
> > Especially when proposing a backport. At present we've provided our
> > -stable recipients no reason to accept the patch.
> >
> > Documentation/process/stable-kernel-rules.rst says "it must fix a real
> > bug that bothers people".
> >
>
> Yes, I agree. I did not include the real bug dmesg in the original
> changelog, which made the stable rationale unclear.
>
> The 9p case above shows that this is a real bug: a userspace-triggered
> teardown path can leave objects in the 9p fcall cache and report the slab
> shutdown warning after umount.
OK, thanks.
> Should I keep Cc: stable in PATCH v2 with this dmesg and
> userspace-visible effect added to the changelog?
Yes please!
prev parent reply other threads:[~2026-08-07 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 12:10 [PATCH] kasan: fix cache shrink race with CPU hotplug Hui Su
2026-08-06 20:51 ` Andrew Morton
2026-08-07 6:50 ` Hui Su
2026-08-07 21:38 ` Andrew Morton [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=20260807143804.24cfd5710208d9a421b0e0e1@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiang1.zhang@intel.com \
--cc=ryabinin.a.a@gmail.com \
--cc=sh_def@163.com \
--cc=stable@vger.kernel.org \
--cc=vincenzo.frascino@arm.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