Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp831213rwl; Fri, 24 Mar 2023 02:34:43 -0700 (PDT) X-Google-Smtp-Source: AK7set/6a+glelQO5/nM8T8I7+uHXTFoV0nbajKPZcX3dH3PvondudCjxd3hoB1vM9du77mOZG+o X-Received: by 2002:a05:6a20:9325:b0:cd:71de:e757 with SMTP id r37-20020a056a20932500b000cd71dee757mr2074076pzh.32.1679650483093; Fri, 24 Mar 2023 02:34:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679650483; cv=none; d=google.com; s=arc-20160816; b=wgjlzXufb5I463oo9Miet4sP3dPrDdLd22O9Dd1y5uQZMy3zb7nkpKPWKuiJUdh6GA ag5TWHIafnR4UcutX5cnbxytOSEuaXALtaR9cZcpMUKZ9ax1FE2yGG20P5Br9VVUcjo5 D5HZ/EU/9xxBewV/HExHElH68dbnYb47F3X3YRKX9u8i4vfK4ekRwgso1yT10LpFCF3s EGkKmYs0CXb39EzPmuS1Pp8M7sFO8oADzLc5ATUeD2oZS1qF01ALaofvHUIKncUO0vAz dBO54F/GMVwRhLVxXctFGZy8LC8HvW/ZtfIrdJ3OZeNERBoZcVgGszTbt7gOkOhoy0AE 8OLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=QcCl5sc+j3IMfbUjl4CDmD357jwtZ469Lo5ySWTEjOU=; b=jXovcLalfcXJT0qRPrghJAt2eKonOLkSLFblybh3I2UtdgNjVv/0eNBQMU4Yq4R3kJ Zl0SBoOge5g1ti0mr9KGZOIlJNKXnLQEsuVyMgRfNLZjISVpear9MMfJvrCZGH2+GgGb zumiLWr/X0i4twCW/tso87Tn2qTZWI06jQ6TmvCaNTWf38uhd9wS8Bs88BYrxGvRsDk5 WXeVap64p9qpdY0Brz98mfJ3L9Gq3UYCCeONHuYKcSwnE7ohM9zjT8MmsBFx6vFnw02b IPw145wCwLUgnKnvnl6ezHIN2JgOWrUmN23Yen9BYHIuS/bhTtTNOCsrocz8R2DXW95a ll8w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="LzVzu8f/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x3-20020a63fe43000000b0050bde92fcbbsi20089134pgj.760.2023.03.24.02.34.30; Fri, 24 Mar 2023 02:34:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="LzVzu8f/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232087AbjCXJZ7 (ORCPT + 99 others); Fri, 24 Mar 2023 05:25:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58924 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231452AbjCXJZ6 (ORCPT ); Fri, 24 Mar 2023 05:25:58 -0400 Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C4E63233D1; Fri, 24 Mar 2023 02:25:56 -0700 (PDT) Received: by mail-ed1-x536.google.com with SMTP id cn12so5287013edb.4; Fri, 24 Mar 2023 02:25:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679649955; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=QcCl5sc+j3IMfbUjl4CDmD357jwtZ469Lo5ySWTEjOU=; b=LzVzu8f/aM6P108G/bMabhIJ01zrRiiqgdW1OWDw11RAIhCW1zh4s1G4SP1oG/2zn+ QfatooAsH+lgIhEPjDca0dB5aGn6WDG9z4KfN9viYmiJEdnp+aRf6+JClgILAV25xjDQ ZAwkF2ed/eokvZIHP5LltaTHlB4kLsptLaVxASS1jVOqN77tPkVoVcTKm3mBGmmCA0Aw VOxLPhaEe9ANpOJrj0E9pCO2DsuoIBiUPazwEJ+bUT4FDCwM9Waq+bvi1ngt2mW9IhpR To1fY2C+mUJ8sNOOl5Et1wgOli9Isn/EtOhvee9T8RWkX8RoP34RlTotuJjk4pZGreJh qqLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679649955; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=QcCl5sc+j3IMfbUjl4CDmD357jwtZ469Lo5ySWTEjOU=; b=ybXDSN9k8CssqKo3CDBPoPnPRjvPsbRL/HSWA1An7BhfebH9CZ/eHaaOGrT8iD/RRF OqI8qUcWeapwP49zOhzl7n6WF8X7QeznXZtIM380kpXCHD9ufA+Ao5VxNceE0a39bYFx 7xFWOZQqgEvy0tQ/KCxDcuPoykog5udc90PBTFioo4G5ovZacb0yRaDLgtAcentnX4KS Cql2KwPOR33Ah+vzhqPaWysH49tM1ZEq5EmfAZuXGbS2QbWKTwYdwWqToKbeduyRGojh E8+oMxSlqQqrWkQhLO33Q4wiUQdJyntFAzXwfMdPoxpKNA05W+Oclc6psXnF4F+6AdVp 4CAQ== X-Gm-Message-State: AO0yUKVsPDjFn+KxvUGJD05zISuVV6LMf5EQqw5yeZKAroBJq0pc4mio MVS53px05gzEDSsJgWM+N+y5eVdu3th66rLMZBA= X-Received: by 2002:a05:6402:3510:b0:4af:62ad:6099 with SMTP id b16-20020a056402351000b004af62ad6099mr6653339edd.2.1679649955024; Fri, 24 Mar 2023 02:25:55 -0700 (PDT) MIME-Version: 1.0 References: <20230323051241.24841-1-lukas.bulwahn@gmail.com> In-Reply-To: From: Lukas Bulwahn Date: Fri, 24 Mar 2023 10:25:43 +0100 Message-ID: Subject: Re: [PATCH] selinux: clean up dead code after removing runtime disable To: Paul Moore Cc: Stephen Smalley , Eric Paris , selinux@vger.kernel.org, kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 23, 2023 at 3:55=E2=80=AFPM Paul Moore wr= ote: > > On Thu, Mar 23, 2023 at 1:12=E2=80=AFAM Lukas Bulwahn wrote: > > > > Commit f22f9aaf6c3d ("selinux: remove the runtime disable functionality= ") > > removes the config SECURITY_SELINUX_DISABLE. This results in some dead = code > > in lsm_hooks.h and a reference in the ABI documentation leading nowhere= as > > the help text is simply gone. > > > > Remove the dead code and dead reference. > > > > Signed-off-by: Lukas Bulwahn > > --- > > Paul, please pick this minor cleanup patch on top of your commit above. > > Hi Lukas, thanks for catching this and sending a patch! For future > reference, you don't need to add a note asking me to pick up this > patch, as long as you send it to the right mailing list - you did - > I'll see it and you'll either get a quick reply when I merge it or a > longer reply with comments/feedback. > > One comment below ... > > > diff --git a/Documentation/ABI/removed/sysfs-selinux-disable b/Document= ation/ABI/removed/sysfs-selinux-disable > > index cb783c64cab3..1ae9587231e1 100644 > > --- a/Documentation/ABI/removed/sysfs-selinux-disable > > +++ b/Documentation/ABI/removed/sysfs-selinux-disable > > @@ -24,6 +24,3 @@ Description: > > SELinux at runtime. Fedora is in the process of removing the > > selinuxfs "disable" node and once that is complete we will star= t the > > slow process of removing this code from the kernel. > > - > > - More information on /sys/fs/selinux/disable can be found under = the > > - CONFIG_SECURITY_SELINUX_DISABLE Kconfig option. > > When I moved the deprecation notice from the "obsolete" to the > "removed" directory I added a note at the top which read: > > "REMOVAL UPDATE: The SELinux checkreqprot functionality was > removed in March 2023, the original deprecation notice is > shown below." > > My goal was to preserve the original notice as much as possible, > including the references to the now defunct Kconfig option, to help > people who are trying to understand how things worked prior to the > removal. > > If you can remove this part of your patch and resubmit I'll happily > merge it into the selinux/next tree. > Okay, I reworked the patch as requested and sent out a PATCH v2: https://lore.kernel.org/all/20230324092114.13907-1-lukas.bulwahn@gmail.com/= T/#u Thanks, Lukas