From: Alyssa Ross <hi@alyssa.is>
To: Alejandro Colomar <alx@kernel.org>
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: [PATCH] man/man7/kernel_lockdown.7: remove Secure Boot untruth
Date: Tue, 3 Feb 2026 20:50:01 +0100 [thread overview]
Message-ID: <20260203195001.20131-1-hi@alyssa.is> (raw)
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")
Signed-off-by: Alyssa Ross <hi@alyssa.is>
---
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
--
2.52.0
next reply other threads:[~2026-02-03 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 19:50 Alyssa Ross [this message]
2026-02-03 19:53 ` [PATCH] man/man7/kernel_lockdown.7: remove Secure Boot untruth 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
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=20260203195001.20131-1-hi@alyssa.is \
--to=hi@alyssa.is \
--cc=alx@kernel.org \
--cc=dhowells@redhat.com \
--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