From: sashiko-bot@kernel.org
To: selinux@vger.kernel.org
Subject: Re: [PATCH v2 3/5] selinux: prevent stale AVC insertions after policy changes
Date: Mon, 09 Nov 2026 15:46:58 +0000 [thread overview]
Message-ID: <sashiko-outbox-205180@kernel.org> (raw)
In-Reply-To: <20261109153802.76176-2-cgoettsche@seltendoof.de>
> From: Christian Göttsche <cgzones@googlemail.com>
>
> A cache miss can compute a decision under the old policy and pass the
> latest_notif check in avc_insert(), then be delayed until after a policy
> change has flushed the AVC and updated latest_notif. Inserting the old
> decision at that point allows subsequent cache hits to keep using the
> old permissions, including permissions revoked by the new policy.
>
> Keep security_compute_av() and avc_insert() in one RCU read-side
> critical section. Both selinux_policy_commit() and security_set_bools()
> publish the new policy and wait for an RCU grace period before flushing
> the AVC. This ensures that insertions based on the old policy finish
> before the flush. The sequence-number check alone cannot provide that
> guarantee, even when it takes the notification lock.
>
> The insertion path uses nonblocking allocations and already runs under
> RCU when called from avc_has_extended_perms(), where the new read-side
> critical section simply nests within the existing one.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109153802.76176-5-cgoettsche@seltendoof.de?part=3
next prev parent reply other threads:[~2026-11-09 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 15:37 [PATCH v2 2/5] selinux: restore the context string on -ESTALE retry Christian Göttsche
2026-11-09 15:37 ` [PATCH v2 3/5] selinux: prevent stale AVC insertions after policy changes Christian Göttsche
2026-11-09 15:46 ` sashiko-bot [this message]
2026-11-09 15:38 ` [PATCH v2 4/5] selinux: keep pending boolean values across policy loads Christian Göttsche
2026-11-09 15:44 ` sashiko-bot
2026-11-09 15:38 ` [PATCH v2 5/5] selinux: do not cache permissive grants after enabling enforcing mode Christian Göttsche
2026-11-09 15:46 ` sashiko-bot
2026-11-09 15:38 ` [PATCH v2 1/5] selinux: zero-initialize permission name array in masked av dump Christian Göttsche
2026-11-09 15:42 ` sashiko-bot
2026-11-09 17:53 ` Stephen Smalley
2026-11-09 15:43 ` [PATCH v2 2/5] selinux: restore the context string on -ESTALE retry 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-205180@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=selinux@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.