linux-kernel - Re: [PATCH] mm, slub: add cpus_read_lock/unlock() for slab_mem_going_offline

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 16 Aug 2021 18:17:51 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     David Hildenbrand <david@...hat.com>
Cc:     qiang.zhang@...driver.com, vbabka@...e.cz,
        akpm@...ux-foundation.org, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm, slub: add cpus_read_lock/unlock() for
 slab_mem_going_offline_callback()

Hi David,

On Mon, 16 Aug 2021 10:04:13 +0200 David Hildenbrand <david@...hat.com> wrote:
>
> On 16.08.21 09:46, qiang.zhang@...driver.com wrote:
> > From: "Qiang.Zhang" <qiang.zhang@...driver.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

Content of type "application/pgp-signature" skipped