From: Andrew Morton <akpm@linux-foundation.org>
To: Hui Su <sh_def@163.com>
Cc: andreyknvl@gmail.com, dvyukov@google.com, glider@google.com,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, qiang1.zhang@intel.com,
ryabinin.a.a@gmail.com, stable@vger.kernel.org,
vincenzo.frascino@arm.com
Subject: Re: [PATCH v2] kasan: fix cache shrink race with CPU hotplug
Date: Sat, 8 Aug 2026 09:53:47 -0700 [thread overview]
Message-ID: <20260808095347.d9335a79ea6513d613784d48@linux-foundation.org> (raw)
In-Reply-To: <20260808093803.3138988-3-sh_def@163.com>
On Sat, 8 Aug 2026 17:38:05 +0800 Hui Su <sh_def@163.com> wrote:
> Thanks Andrew,
>
> On Sat, Aug 08, 2026 at 12:39:21AM -0700, Andrew Morton wrote:
> > AI review suggests that there's a pre-existing quarantine_size
> > accounting flaw later in this function:
> >
> > https://sashiko.dev/#/patchset/20260808031459.3032812-1-sh_def@163.com
> >
> > If true, I'm surprised this hasn't yet been reported.
>
> I'll take a closer look at this. If it turns out to be a real issue,
> I'll send a separate patch since it's pre-existing and unrelated to the
> hotplug race fix.
>
> > Also, I'd like to see a need_resched() wrapping that expensive
> >
> > /* Scanning whole quarantine can take a while. */
> > raw_spin_unlock_irqrestore(&quarantine_lock, flags);
> > cond_resched();
> > raw_spin_lock_irqsave(&quarantine_lock, flags);
>
> Good point, that makes sense. Would you prefer that I fold this into a
> v3 of this patch, or send it as a separate follow-up patch?
Separate patches, please. One patch per concept.
prev parent reply other threads:[~2026-08-08 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 3:14 [PATCH v2] kasan: fix cache shrink race with CPU hotplug Hui Su
2026-08-08 7:39 ` Andrew Morton
2026-08-08 9:38 ` Hui Su
2026-08-08 16:53 ` 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=20260808095347.d9335a79ea6513d613784d48@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