All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH 1/4] apparmor: move the feature tables to a header
Date: Tue, 17 Nov 2026 13:55:44 +0000	[thread overview]
Message-ID: <sashiko-outbox-218909@kernel.org> (raw)
In-Reply-To: <20261117135042.78238-2-maxime.belair@canonical.com>

> The tables that describe the securityfs features directory are spread
> over apparmorfs.c, capability.c, net.c and resource.c. Move them to
> include/features.h, so that a later patch can also build them into a
> host program, which writes the feature set to a file when the kernel
> is built.
> 
> Three of the tables use a generated mask. Collect the masks in
> feature_masks.h, apart from the name tables they are generated with.
> 
> The entries are moved as they are, and the content of the features
> directory does not change.
> 
> 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=1


  reply	other threads:[~2026-11-17 13:55 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 [this message]
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
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-218909@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.