From: jmorris@namei.org (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 02/24] Add the ability to lock down access to the running kernel image
Date: Thu, 6 Apr 2017 18:44:16 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1704061840090.12226@namei.org> (raw)
In-Reply-To: <149141221365.31282.16276273075946694481.stgit@warthog.procyon.org.uk>
On Wed, 5 Apr 2017, David Howells wrote:
> +#include <linux/security.h>
> +#include <linux/export.h>
> +
> +static __read_mostly bool kernel_locked_down;
How about marking this __ro_after_init if ALLOW_LOCKDOWN_LIFT is not
configured?
--
James Morris
<jmorris@namei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-04-06 8:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 17:09 [PATCH 00/24] Kernel lockdown David Howells
2017-04-05 17:10 ` [PATCH 01/24] efi: Add EFI_SECURE_BOOT bit David Howells
2017-04-05 17:10 ` [PATCH 02/24] Add the ability to lock down access to the running kernel image David Howells
2017-04-06 8:44 ` James Morris [this message]
2017-04-06 10:43 ` David Howells
2017-04-06 21:55 ` James Morris
2017-04-05 17:10 ` [PATCH 03/24] efi: Lock down the kernel if booted in secure boot mode David Howells
2017-04-05 17:10 ` [PATCH 04/24] Enforce module signatures if the kernel is locked down David Howells
2017-04-05 17:10 ` [PATCH 05/24] Restrict /dev/mem and /dev/kmem when " David Howells
2017-04-05 17:10 ` [PATCH 06/24] Add a sysrq option to exit secure boot mode David Howells
2017-04-05 17:10 ` [PATCH 07/24] kexec: Disable at runtime if the kernel is locked down David Howells
2017-04-05 17:11 ` [PATCH 08/24] Copy secure_boot flag in boot params across kexec reboot David Howells
2017-04-05 17:11 ` [PATCH 09/24] kexec_file: Disable at runtime if securelevel has been set David Howells
2017-04-05 17:11 ` [PATCH 10/24] hibernate: Disable when the kernel is locked down David Howells
2017-04-05 17:11 ` [PATCH 11/24] uswsusp: " David Howells
2017-04-05 17:11 ` [PATCH 12/24] PCI: Lock down BAR access " David Howells
2017-04-05 17:11 ` [PATCH 13/24] x86: Lock down IO port " David Howells
2017-04-05 17:12 ` [PATCH 14/24] x86: Restrict MSR " David Howells
2017-04-05 17:34 ` Kees Cook
2017-04-05 17:12 ` [PATCH 15/24] asus-wmi: Restrict debugfs interface " David Howells
2017-04-05 17:12 ` [PATCH 16/24] ACPI: Limit access to custom_method " David Howells
2017-04-05 17:12 ` [PATCH 17/24] acpi: Ignore acpi_rsdp kernel param when the kernel has been " David Howells
2017-04-05 17:12 ` [PATCH 18/24] acpi: Disable ACPI table override if the kernel is " David Howells
2017-04-05 17:12 ` [PATCH 19/24] acpi: Disable APEI error injection " David Howells
2017-04-05 19:57 ` [PATCH 00/24] Kernel lockdown David Howells
2017-04-06 8:25 ` James Morris
2017-04-06 8:37 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2017-04-05 20:14 David Howells
2017-04-05 20:14 ` [PATCH 02/24] Add the ability to lock down access to the running kernel image David Howells
2017-04-05 17:07 [PATCH 00/24] Kernel lockdown David Howells
2017-04-05 17:07 ` [PATCH 02/24] Add the ability to lock down access to the running kernel image David Howells
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=alpine.LRH.2.20.1704061840090.12226@namei.org \
--to=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
/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