From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Hildenbrand <david@redhat.com>
Cc: qiang.zhang@windriver.com, vbabka@suse.cz,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm, slub: add cpus_read_lock/unlock() for slab_mem_going_offline_callback()
Date: Mon, 16 Aug 2021 18:17:51 +1000 [thread overview]
Message-ID: <20210816181751.17f98cc2@canb.auug.org.au> (raw)
In-Reply-To: <ef944ea5-c3cb-24e5-1ff8-b8e1008fa6ed@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Hi David,
On Mon, 16 Aug 2021 10:04:13 +0200 David Hildenbrand <david@redhat.com> wrote:
>
> On 16.08.21 09:46, qiang.zhang@windriver.com wrote:
> > From: "Qiang.Zhang" <qiang.zhang@windriver.com>
> >
> > The flush_all_cpus_locked() should be called with cpus_read_lock/unlock(),
> > ensure flush_cpu_slab() can be executed on schedule_on CPU.
> >
> > Fixes: 1c84f3c91640 ("mm, slub: fix memory and cpu hotplug related lock ordering issues")
>
> Which branch contains this commit? At least not linux.git or linux-next
It is Andrew's mmotm which is included in linux-next but gets rebased
often, so, for example, that SHA1 is no longer valid in linux-next
today (is is now fd917c6407fb).
This (unfortunately) make Fixes tags less useful for mmotm :-(
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-08-16 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 7:46 qiang.zhang
2021-08-16 8:04 ` David Hildenbrand
2021-08-16 8:10 ` Zhang, Qiang
2021-08-16 8:17 ` Stephen Rothwell [this message]
2021-08-16 8:23 ` David Hildenbrand
2021-08-17 7:57 ` Vlastimil Babka
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=20210816181751.17f98cc2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiang.zhang@windriver.com \
--cc=vbabka@suse.cz \
/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