From: Fan Wu <wufan@kernel.org>
To: linux-security-module@vger.kernel.org
Subject: [PATCH 0/6] ipe: cleanups, an audit fix and updated links
Date: Fri, 2 Oct 2026 19:51:29 -0700 [thread overview]
Message-ID: <20261003025135.3666767-1-wufan@kernel.org> (raw)
This series contains small IPE cleanups, a fix for an extra empty audit
record, and updated documentation links.
Patches 1-4 are cleanups with no functional change.
Patch 5 fixes an extra empty audit record on enforcement changes.
Patch 6 points the documentation to the new IPE website and test suite
repository.
Fan Wu (6):
ipe: constify token_default()
ipe: use designated initializers for audit name tables
ipe: check parser token table sizes
ipe: correct policy text ownership comment
ipe: fix enforcement audit
ipe: update the project and test suite links
Documentation/admin-guide/LSM/ipe.rst | 2 +-
Documentation/security/ipe.rst | 2 +-
security/ipe/audit.c | 52 ++++++++++++---------------
security/ipe/policy.c | 2 +-
security/ipe/policy_parser.c | 10 +++++-
5 files changed, 34 insertions(+), 34 deletions(-)
base-commit: 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e
--
2.55.0
next reply other threads:[~2026-10-03 2:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 2:51 Fan Wu [this message]
2026-10-03 2:51 ` [PATCH 1/6] ipe: constify token_default() Fan Wu
2026-10-03 2:56 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 2/6] ipe: use designated initializers for audit name tables Fan Wu
2026-10-03 2:59 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 3/6] ipe: check parser token table sizes Fan Wu
2026-10-03 2:56 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 4/6] ipe: correct policy text ownership comment Fan Wu
2026-10-03 2:57 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 5/6] ipe: fix enforcement audit Fan Wu
2026-10-03 2:55 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 6/6] ipe: update the project and test suite links Fan Wu
2026-10-03 2:55 ` sashiko-bot
2026-10-06 16:59 ` [PATCH 0/6] ipe: cleanups, an audit fix and updated links Fan Wu
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=20261003025135.3666767-1-wufan@kernel.org \
--to=wufan@kernel.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 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.