linux-kernel - Re: lockdep warns: cpu_hotplug_lock.rw_sem --> slab

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.DEB.2.21.1912092029080.6020@www.lameter.com>
Date:   Mon, 9 Dec 2019 20:33:13 +0000 (UTC)
From:   Christopher Lameter <cl@...ux.com>
To:     Daniel Wagner <dwagner@...e.de>
cc:     Pekka Enberg <penberg@...nel.org>,
        David Rientjes <rientjes@...gle.com>,
        Joonsoo Kim <iamjoonsoo.kim@....com>,
        Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: lockdep warns: cpu_hotplug_lock.rw_sem --> slab_mutex -->
 kn->count#39

On Mon, 9 Dec 2019, Daniel Wagner wrote:

> [    5.038862]
> [    5.038862] -> #2 (kn->count#39){++++}:
> [    5.039329]        __kernfs_remove+0x240/0x2e0
> [    5.039717]        kernfs_remove_by_name_ns+0x3c/0x80
> [    5.040159]        sysfs_slab_add+0x184/0x250

sysfs_slab_add should not be called under any lock. But it happens during
an initcall (sysfs_slab_init) when the kmalloc slab array is being set up.

And the problems results from a hotplug event? During system bringup when
the slab caches have not been setup yet?

Is this really something that can happen?