From: David Hildenbrand <david@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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 10:23:49 +0200 [thread overview]
Message-ID: <e9b22a8a-e5d2-955f-65b9-1e30efe24f81@redhat.com> (raw)
In-Reply-To: <20210816181751.17f98cc2@canb.auug.org.au>
On 16.08.21 10:17, Stephen Rothwell wrote:
> 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
Maybe I am blind or need more coffee:
https://www.ozlabs.org/~akpm/mmotm/series
> 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 :-(
Right, and it somewhat makes sense, because Andrew will actually squash
patches before sending them further upstream.
Ideally, such fixes should be discussed in the respective patch series,
because before they go upstream, they are still under development.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-08-16 8:23 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
2021-08-16 8:23 ` David Hildenbrand [this message]
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=e9b22a8a-e5d2-955f-65b9-1e30efe24f81@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiang.zhang@windriver.com \
--cc=sfr@canb.auug.org.au \
--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