From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8FAC8C43603 for ; Mon, 9 Dec 2019 20:33:15 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 68EF42068E for ; Mon, 9 Dec 2019 20:33:15 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 68EF42068E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 05EC56B288C; Mon, 9 Dec 2019 15:33:15 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 00F956B288D; Mon, 9 Dec 2019 15:33:14 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E67726B288E; Mon, 9 Dec 2019 15:33:14 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0126.hostedemail.com [216.40.44.126]) by kanga.kvack.org (Postfix) with ESMTP id CCCAF6B288C for ; Mon, 9 Dec 2019 15:33:14 -0500 (EST) Received: from smtpin20.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with SMTP id 96F03443C for ; Mon, 9 Dec 2019 20:33:14 +0000 (UTC) X-FDA: 76246752708.20.beef58_567a24a4e1a35 X-HE-Tag: beef58_567a24a4e1a35 X-Filterd-Recvd-Size: 1779 Received: from gentwo.org (gentwo.org [3.19.106.255]) by imf09.hostedemail.com (Postfix) with ESMTP for ; Mon, 9 Dec 2019 20:33:14 +0000 (UTC) Received: by gentwo.org (Postfix, from userid 1002) id B1FD53EEC7; Mon, 9 Dec 2019 20:33:13 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by gentwo.org (Postfix) with ESMTP id B06213ED44; Mon, 9 Dec 2019 20:33:13 +0000 (UTC) Date: Mon, 9 Dec 2019 20:33:13 +0000 (UTC) From: Christopher Lameter X-X-Sender: cl@www.lameter.com To: Daniel Wagner cc: Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: lockdep warns: cpu_hotplug_lock.rw_sem --> slab_mutex --> kn->count#39 In-Reply-To: <20191209182418.7vxer6vmre67ewvt@beryllium.lan> Message-ID: References: <20191209182418.7vxer6vmre67ewvt@beryllium.lan> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: 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?