From: Vitaly Chikunov <vt@altlinux.org>
To: ALT Linux kernel packages development <devel-kernel@lists.altlinux.org>
Subject: Re: [d-kernel] [PATCH 2/6] security: lockdown: expose security_lock_kernel_down function
Date: Sat, 9 May 2026 03:20:41 +0300
Message-ID: <af53JULbo3AvBJno@altlinux.org> (raw)
In-Reply-To: <20260506173722.1012394-3-egori@altlinux.org>
On Wed, May 06, 2026 at 08:37:18PM +0300, Egor Ignatov wrote:
> From: Jeremy Cline <jcline@redhat.com>
>
> In order to automatically lock down kernels running on UEFI machines
> booted in Secure Boot mode, expose the security_lock_kernel_down() function.
>
> Based on Fedora patches:
> - security: lockdown: expose a hook to lock the kernel down
> - efi,lockdown: fix kernel lockdown on Secure Boot
Но, у второго патча автор Ondrej Mosnacek, а мы скорее берем его
изменения, а не из первого патча.
Кроме того, тэг `Signed-off-by` не укатает на авторство.
Может лучше указать во From себя, но добавить:
Based-on-a-patch-by: Jeremy Cline <jcline@redhat.com>
Based-on-a-patch-by: Ondrej Mosnacek <omosnace@redhat.com>
Такое есть в ядре, хоть и редко.
>
> Signed-off-by: Jeremy Cline <jcline@redhat.com>
> Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
> Signed-off-by: Egor Ignatov <egori@altlinux.org>
> ---
> include/linux/security.h | 9 +++++++++
> security/lockdown/lockdown.c | 11 +++++++++++
> 2 files changed, 20 insertions(+)
>
> diff --git a/include/linux/security.h b/include/linux/security.h
> index ee88dd2d2d..5c816f0b8b 100644
> --- a/include/linux/security.h
> +++ b/include/linux/security.h
> @@ -2405,4 +2405,13 @@ static inline void security_initramfs_populated(void)
> }
> #endif /* CONFIG_SECURITY */
>
> +#ifdef CONFIG_SECURITY_LOCKDOWN_LSM
> +extern int security_lock_kernel_down(const char *where, enum lockdown_reason level);
> +#else
> +static inline int security_lock_kernel_down(const char *where, enum lockdown_reason level)
> +{
> + return 0;
> +}
> +#endif /* CONFIG_SECURITY_LOCKDOWN_LSM */
> +
> #endif /* ! __LINUX_SECURITY_H */
> diff --git a/security/lockdown/lockdown.c b/security/lockdown/lockdown.c
> index 8d46886d2c..14a9cdff94 100644
> --- a/security/lockdown/lockdown.c
> +++ b/security/lockdown/lockdown.c
> @@ -72,6 +72,17 @@ static int lockdown_is_locked_down(enum lockdown_reason what)
> return 0;
> }
>
> +/**
> + * security_lock_kernel_down() - Put the kernel into lock-down mode.
> + *
> + * @where: Where the lock-down is originating from (e.g. command line option)
> + * @level: The lock-down level (can only increase)
> + */
> +int security_lock_kernel_down(const char *where, enum lockdown_reason level)
> +{
> + return lock_kernel_down(where, level);
> +}
> +
> static struct security_hook_list lockdown_hooks[] __ro_after_init = {
> LSM_HOOK_INIT(locked_down, lockdown_is_locked_down),
> };
> --
> 2.50.1
>
> _______________________________________________
> devel-kernel mailing list
> devel-kernel@lists.altlinux.org
> https://lists.altlinux.org/mailman/listinfo/devel-kernel
next prev parent reply other threads:[~2026-05-09 0:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 17:37 [d-kernel] [PATCH 0/6] [7.0, 7.1] Lock down the kernel if booted in Secure Boot mode Egor Ignatov
2026-05-06 17:37 ` [d-kernel] [PATCH 1/6] mtd: phram, slram: Disable when the kernel is locked down Egor Ignatov
2026-05-08 23:43 ` Vitaly Chikunov
2026-05-06 17:37 ` [d-kernel] [PATCH 2/6] security: lockdown: expose security_lock_kernel_down function Egor Ignatov
2026-05-09 0:20 ` Vitaly Chikunov [this message]
2026-05-06 17:37 ` [d-kernel] [PATCH 3/6] efi: Add an EFI_SECURE_BOOT flag to indicate secure boot mode Egor Ignatov
2026-05-06 17:37 ` [d-kernel] [PATCH 4/6] efi: Lock down the kernel if booted in " Egor Ignatov
2026-05-09 0:24 ` Vitaly Chikunov
2026-05-06 17:37 ` [d-kernel] [PATCH 5/6] efi: determine and pass Secure Boot state via FDT Egor Ignatov
2026-05-09 0:28 ` Vitaly Chikunov
2026-05-06 17:37 ` [d-kernel] [PATCH 6/6] config: Enable LOCK_DOWN_IN_EFI_SECURE_BOOT Egor Ignatov
2026-05-09 0:34 ` Vitaly Chikunov
2026-05-08 23:01 ` [d-kernel] [PATCH 0/6] [7.0, 7.1] Lock down the kernel if booted in Secure Boot mode Vitaly Chikunov
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=af53JULbo3AvBJno@altlinux.org \
--to=vt@altlinux.org \
--cc=devel-kernel@lists.altlinux.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
ALT Linux kernel packages development
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel-kernel/0 devel-kernel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel-kernel devel-kernel/ http://lore.altlinux.org/devel-kernel \
devel-kernel@altlinux.org devel-kernel@altlinux.ru devel-kernel@altlinux.com
public-inbox-index devel-kernel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel-kernel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git