From: Alejandro Colomar <alx@kernel.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
David Howells <dhowells@redhat.com>,
Nicolas Bouchinet <nicolas.bouchinet@oss.cyber.gouv.fr>,
Xiu Jianfeng <xiujianfeng@huawei.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, 3 Feb 2026 21:27:44 +0100 [thread overview]
Message-ID: <aYJZ31jO5ZE1Z6Xp@devuan> (raw)
In-Reply-To: <aYJSDDwK1T9xxca1@mbp.qyliss.net>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
Hi Alyssa,
On 2026-02-03T20:53:33+0100, Alyssa Ross wrote:
> On Tue, Feb 03, 2026 at 08:50:01PM +0100, 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.
> >
> > 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")
I've now CCed you in an email documenting the format we use for these.
It should be:
Fixes: bb509e6fcbae (2020-10-16; "kernel_lockdown.7: New page documenting the Kernel Lockdown feature")
I'll amend that myself.
> > Signed-off-by: Alyssa Ross <hi@alyssa.is>
>
> Just noticed there's a long-open bug for this as well, so additionally:
>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=213577
Thanks! I'll keep the patch for a few days, in case anyone wants to
comment.
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-03 20:27 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 [this message]
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
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=aYJZ31jO5ZE1Z6Xp@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