From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=113.46.200.219 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793692293; b=kDxKgcn7epXrgSP5i1Bo+qqBeOQXoa/82bll3qPkdUsoCqb4veDso2xRCo0mUbMw8EBw ss+atq06H2/a+9t6kgYL+kADimL+hLCi6AnKYmyZD/PkNzbp7HYMn2K3JjYVDtzDJr0Ee iZ8NqlAlNk+fdbkusA8Fv0Fvzu/lIidq69xhuBaIZ6rTQrxojpDcMziHpTiE4942ZorSs 7ZyaSyJFHXIwsUYzLFQg4B8LyUR3rkYfv6OJQt486EVaHEdeCy/51A38phPFIqjDTqUR8 O8yVRH/fFy+SK3IPZIn07f1W1o1sCeP6COfs6bwzs1r7knF+4S5uz0ngLScSDOXlRCw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793692293; h=DMARC-Filter:dkim-signature:Received:Received:Received:From:To:CC: Subject:Date:Message-ID:X-Mailer:In-Reply-To:References:MIME-Version: Content-Type:X-Originating-IP:X-ClientProxiedBy; bh=U0OKKZb0bS0e4DptnMS2LcajkhFw1BOADafcvXSHktE=; b=5imIcILGMPzhYdVVMsTHVxRQIXNgK5+CWAy50U5Gl/XYtS5aUSx8gcruD61RDE1Pu9fJ VzRWC6XlsPuiWFErRm3hAv7xE4RvPK/UH33gPRq40eeK5tdB23jmuYfIRuSv+vJKdXfmE oXFt+p46u/Mf5aJoUERaB71K0BxpuALwxJDLb/iyici9+hRzmeDncvoEXo9TRcgPnXcD7 /m2kb0k5b92TAaeWykRIZ3M1uSBdO2QpL/rZZ3faEvfVAWL+kk/Z1X2kGX62dPk+GHNMH XyVA+1Mw/SZqImJ/6jxUFtem/w86wwrk+pgOvVHFYkRx5y7lAfvBGTFMY3VvssE2eLA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; dkim=pass header.d=huawei.com header.i=@huawei.com header.a=rsa-sha256 header.s=dkim header.b=OknLY2ee; arc=none smtp.remote-ip=113.46.200.219 Received: from canpmsgout04.his.huawei.com (canpmsgout04.his.huawei.com [113.46.200.219]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D148C606A334; Tue, 3 Nov 2026 07:51:30 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org D148C606A334 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=huawei.com header.i=@huawei.com header.a=rsa-sha256 header.s=dkim header.b=OknLY2ee dkim-signature: v=1; a=rsa-sha256; d=huawei.com; s=dkim; c=relaxed/relaxed; q=dns/txt; h=From; bh=U0OKKZb0bS0e4DptnMS2LcajkhFw1BOADafcvXSHktE=; b=OknLY2eeRRyF2bepRVyLhUyH44H8O2MDnYYxe+Av9fxUoRvpYU8B3mCQe4jpk4MRwx6drX4bQ qDFnC0Z+aRIAsPi0B1Y0J9WZHkUBbtVLA1yPKsSk+65d7PQ+P5C8MsS0EaIHiEmT0FPJ0qI3Ggp P4lAYIcdRstIr7+m+TLZl3k= Received: from mail.maildlp.com (unknown [172.19.163.0]) by canpmsgout04.his.huawei.com (SkyGuard) with ESMTPS id 4jJgkF4JYBz1prPP; Tue, 3 Nov 2026 15:51:17 +0800 (CST) Received: from whupemk100010.china.huawei.com (unknown [7.152.184.41]) by mail.maildlp.com (Postfix) with ESMTPS id 89A2F40561; Tue, 3 Nov 2026 15:51:21 +0800 (CST) Received: from octopus.huawei.com (10.67.174.191) by whupemk100010.china.huawei.com (7.152.184.41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.45; Tue, 3 Nov 2026 15:51:20 +0800 From: Cai Xinchen To: , , , , , , CC: , , , , Subject: [PATCH -next 4/9] lockdown: select SECURITYFS Date: Tue, 3 Nov 2026 16:24:16 +0800 Message-ID: <20261103082421.3033195-5-caixinchen1@huawei.com> X-Mailer: git-send-email 2.18.0.huawei.25 In-Reply-To: <20261103082421.3033195-1-caixinchen1@huawei.com> References: <20261103082421.3033195-1-caixinchen1@huawei.com> X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain X-ClientProxiedBy: kwepems100002.china.huawei.com (7.221.188.206) To whupemk100010.china.huawei.com (7.152.184.41) The lockdown LSM exposes /sys/kernel/security/lockdown, but it does not select SECURITYFS. If SECURITYFS is disabled, securityfs_create_file() returns -ENODEV, lockdown_secfs_init() fails and the LSM framework logs: failed LSM lockdown core initcall with errno -19 while the sysfs interface advertised by the Kconfig help text is missing. Select SECURITYFS like the other LSMs that create securityfs entries (AppArmor, SafeSetID, TOMOYO and IMA) already do. Signed-off-by: Cai Xinchen --- security/lockdown/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/security/lockdown/Kconfig b/security/lockdown/Kconfig index e84ddf484010..82b69d8253bd 100644 --- a/security/lockdown/Kconfig +++ b/security/lockdown/Kconfig @@ -2,6 +2,7 @@ config SECURITY_LOCKDOWN_LSM bool "Basic module for enforcing kernel lockdown" depends on SECURITY select MODULE_SIG if MODULES + select SECURITYFS help Build support for an LSM that enforces a coarse kernel lockdown behaviour. -- 2.18.0.huawei.25