From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH 3/4] apparmor: write the feature set to a file at build time
Date: Tue, 17 Nov 2026 14:00:55 +0000 [thread overview]
Message-ID: <sashiko-outbox-218917@kernel.org> (raw)
In-Reply-To: <20261117135042.78238-4-maxime.belair@canonical.com>
> apparmor_parser compiles policy for the feature set of the kernel,
> which libapparmor reads from /sys/kernel/security/apparmor/features,
> and the policy cache is keyed on that set. The cache for a kernel can
> therefore only be filled once that kernel runs, and the first boot
> into a kernel with a new feature set compiles all of the policy.
>
> Every entry of the features directory comes from a static table of
> constants. So write the set to security/apparmor/features when the
> kernel is built, in the format that libapparmor flattens the directory
> to. Policy can then be compiled when a kernel is installed:
>
> apparmor_parser --kernel-features=<file> ...
>
> Signed-off-by: Maxime Bélair <maxime.belair@canonical.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261117135042.78238-1-maxime.belair@canonical.com?part=3
next prev parent reply other threads:[~2026-11-17 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 13:50 [PATCH 0/4] apparmor: provide the kernel feature set at build time Maxime Bélair
2026-11-17 13:50 ` [PATCH 1/4] apparmor: move the feature tables to a header Maxime Bélair
2026-11-17 13:55 ` sashiko-bot
2026-11-17 13:50 ` [PATCH 2/4] apparmor: make the feature tables build without kernel headers Maxime Bélair
2026-11-17 13:55 ` sashiko-bot
2026-11-17 13:50 ` [PATCH 3/4] apparmor: write the feature set to a file at build time Maxime Bélair
2026-11-17 14:00 ` sashiko-bot [this message]
2026-11-17 13:50 ` [PATCH 4/4] kbuild: install the AppArmor feature set with the modules Maxime Bélair
2026-11-17 13:58 ` sashiko-bot
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=sashiko-outbox-218917@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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