public inbox for linux-security-module@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Nicolas Bouchinet <nicolas.bouchinet@oss.cyber.gouv.fr>
Cc: Xiu Jianfeng <xiujianfeng@huawei.com>, Alyssa Ross <hi@alyssa.is>,
	 Heinrich Schuchardt <xypron.glpk@gmx.de>,
	David Howells <dhowells@redhat.com>,
	 linux-security-module@vger.kernel.org,
	linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man7/kernel_lockdown.7: remove Secure Boot untruth
Date: Tue, 10 Feb 2026 23:06:55 +0100	[thread overview]
Message-ID: <aYurp8P0HLVdpIir@devuan> (raw)
In-Reply-To: <aYYP23WUyydsMGyx@archlinux>

[-- Attachment #1: Type: text/plain, Size: 2827 bytes --]

Hi all,

On 2026-02-06T17:08:35+0100, Nicolas Bouchinet wrote:
> On Thu, Feb 05, 2026 at 07:48:02PM +0800, Xiu Jianfeng wrote:
> > On 2/4/2026 3:50 AM, Alyssa Ross wrote:
> > > This is true for Fedora, where this page was sourced from, but I don't
> > > believe it has ever been true for the mainline kernel, because Linus
> > > rejected it.
> > 
> > Yeah, I also found this issue not long ago, but I haven't had time to submit
> > a fix patch yet.
> > 
> > > 
> > > Link: https://bbs.archlinux.org/viewtopic.php?pid=2088704#p2088704
> > > Link: https://lore.kernel.org/lkml/CA+55aFzYbpRAdma0PvqE+9ygySuKzNKByqOzzMufBoovXVnfPw@mail.gmail.com/
> > > Fixes: bb509e6fc ("kernel_lockdown.7: New page documenting the Kernel Lockdown feature")
> > > Signed-off-by: Alyssa Ross <hi@alyssa.is>
> > 
> > I am not sure if appropriate to add my ACK here, if needed, feel free to
> > add:
> > 
> > Acked-by: Xiu Jianfeng <xiujianfeng@huawei.com>
> > 
> 
> You can also add mine too :
> 
> Acked-by: Nicolas Bouchinet <nicolas.bouchinet@oss.cyber.gouv.fr>

Thanks!  I've applied the patch.

    Link: <https://bbs.archlinux.org/viewtopic.php?pid=2088704#p2088704>
    Link: <https://lore.kernel.org/lkml/CA+55aFzYbpRAdma0PvqE+9ygySuKzNKByqOzzMufBoovXVnfPw@mail.gmail.com/>
    Fixes: bb509e6fcbae (2020-10-16; "kernel_lockdown.7: New page documenting the Kernel Lockdown feature")
    Signed-off-by: Alyssa Ross <hi@alyssa.is>
    Message-ID: <20260203195001.20131-1-hi@alyssa.is>
    Acked-by: Xiu Jianfeng <xiujianfeng@huawei.com>
    Message-ID: <aa62e24c-537e-4141-9507-37cd0af19dfc@huawei.com>
    Acked-by: Nicolas Bouchinet <nicolas.bouchinet@oss.cyber.gouv.fr>
    Message-ID: <aYYP23WUyydsMGyx@archlinux>
    Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
    Cc: David Howells <dhowells@redhat.com>
    Cc: <linux-security-module@vger.kernel.org>
    Signed-off-by: Alejandro Colomar <alx@kernel.org>


Have a lovely night!
Alex

> 
> Thank you in advance,
> 
> Nicolas
> 
> > > ---
> > >   man/man7/kernel_lockdown.7 | 3 ---
> > >   1 file changed, 3 deletions(-)
> > > 
> > > diff --git a/man/man7/kernel_lockdown.7 b/man/man7/kernel_lockdown.7
> > > index 5090484ea..5986c8f01 100644
> > > --- a/man/man7/kernel_lockdown.7
> > > +++ b/man/man7/kernel_lockdown.7
> > > @@ -23,9 +23,6 @@ Lockdown: X: Y is restricted, see man kernel_lockdown.7
> > >   .in
> > >   .P
> > >   where X indicates the process name and Y indicates what is restricted.
> > > -.P
> > > -On an EFI-enabled x86 or arm64 machine, lockdown will be automatically enabled
> > > -if the system boots in EFI Secure Boot mode.
> > >   .\"
> > >   .SS Coverage
> > >   When lockdown is in effect, a number of features are disabled or have their
> > 

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-02-10 22:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 19:50 [PATCH] man/man7/kernel_lockdown.7: remove Secure Boot untruth Alyssa Ross
2026-02-03 19:53 ` Alyssa Ross
2026-02-03 20:27   ` Alejandro Colomar
2026-02-03 20:47     ` Heinrich Schuchardt
2026-02-10 22:03       ` Alejandro Colomar
2026-02-04  9:03 ` Nicolas Bouchinet
2026-02-05 11:48 ` Xiu Jianfeng
2026-02-05 13:10   ` Alejandro Colomar
2026-02-06 16:08   ` Nicolas Bouchinet
2026-02-10 22:06     ` Alejandro Colomar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aYurp8P0HLVdpIir@devuan \
    --to=alx@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=hi@alyssa.is \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=nicolas.bouchinet@oss.cyber.gouv.fr \
    --cc=xiujianfeng@huawei.com \
    --cc=xypron.glpk@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox