From: Andrea Parri <parri.andrea@gmail.com>
To: Kees Cook <kees@kernel.org>
Cc: Andrea Parri <parri.andrea@gmail.com>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>, Shuah Khan <shuah@kernel.org>,
Rodrigo Campos <rodrigo@kinvolk.io>,
Christian Brauner <brauner@kernel.org>,
Tycho Andersen <tycho@tycho.pizza>,
Sargun Dhillon <sargun@sargun.me>, Hui Peng <benquike@gmail.com>,
Bradley Morgan <brads@mainlining.org>,
Cong Wang <cwang@multikernel.io>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
bpf@vger.kernel.org
Subject: [PATCH 3/4] seccomp: add a helper to move a notification to SENT
Date: Wed, 4 Nov 2026 11:37:33 +0100 [thread overview]
Message-ID: <20261104103736.71956-4-parri.andrea@gmail.com> (raw)
In-Reply-To: <20261104103736.71956-1-parri.andrea@gmail.com>
seccomp_notify_recv(), seccomp_handle_addfd() and seccomp_notify_addfd()
each move a user notification to the SENT state. The notification then
accepts a reply, so each site must also wake EPOLLOUT waiters. Both
addfd paths have missed that wakeup before.
Move the state change and the wakeup into seccomp_notify_set_sent() so a
new path cannot set SENT without waking poll waiters. The helper asserts
that notify_lock is held, as all three callers already do.
No functional change intended.
The change was written with the help of an LLM.
Cc: stable@vger.kernel.org # 7.4.x
Signed-off-by: Andrea Parri <parri.andrea@gmail.com>
---
kernel/seccomp.c | 21 +++++++++++++--------
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/kernel/seccomp.c b/kernel/seccomp.c
index ee94a071736ef..75a758128db2d 100644
--- a/kernel/seccomp.c
+++ b/kernel/seccomp.c
@@ -1125,6 +1125,15 @@ static u64 seccomp_next_notify_id(struct seccomp_filter *filter)
return filter->notif->next_id++;
}
+/* A notification in SENT state accepts a reply; tell poll waiters. */
+static void seccomp_notify_set_sent(struct seccomp_filter *filter,
+ struct seccomp_knotif *n)
+{
+ lockdep_assert_held(&filter->notify_lock);
+ n->state = SECCOMP_NOTIFY_SENT;
+ wake_up_poll(&filter->wqh, EPOLLOUT | EPOLLWRNORM);
+}
+
static void seccomp_handle_addfd(struct seccomp_filter *filter,
struct seccomp_kaddfd *addfd,
struct seccomp_knotif *n)
@@ -1145,8 +1154,7 @@ static void seccomp_handle_addfd(struct seccomp_filter *filter,
if (addfd->ioctl_flags & SECCOMP_ADDFD_FLAG_SEND) {
/* If we fail reset and return an error to the notifier */
if (fd < 0) {
- n->state = SECCOMP_NOTIFY_SENT;
- wake_up_poll(&filter->wqh, EPOLLOUT | EPOLLWRNORM);
+ seccomp_notify_set_sent(filter, n);
} else {
/* Return the FD we just added */
n->flags = 0;
@@ -1600,8 +1608,7 @@ static long seccomp_notify_recv(struct seccomp_filter *filter,
unotif.pid = task_pid_vnr(knotif->task);
unotif.data = *(knotif->data);
- knotif->state = SECCOMP_NOTIFY_SENT;
- wake_up_poll(&filter->wqh, EPOLLOUT | EPOLLWRNORM);
+ seccomp_notify_set_sent(filter, knotif);
ret = 0;
out:
mutex_unlock(&filter->notify_lock);
@@ -1824,10 +1831,8 @@ static long seccomp_notify_addfd(struct seccomp_filter *filter,
ret = kaddfd.ret;
} else {
list_del(&kaddfd.list);
- if (addfd.flags & SECCOMP_ADDFD_FLAG_SEND) {
- knotif->state = SECCOMP_NOTIFY_SENT;
- wake_up_poll(&filter->wqh, EPOLLOUT | EPOLLWRNORM);
- }
+ if (addfd.flags & SECCOMP_ADDFD_FLAG_SEND)
+ seccomp_notify_set_sent(filter, knotif);
}
out_unlock:
--
2.53.0
next prev parent reply other threads:[~2026-11-04 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 10:37 [PATCH 0/4] seccomp: fix user-notification state transitions Andrea Parri
2026-11-04 10:37 ` [PATCH 1/4] seccomp: wake poll waiters after failed addfd send Andrea Parri
2026-11-04 16:19 ` Tycho Andersen
2026-11-04 10:37 ` [PATCH 2/4] seccomp: wake poll waiters after interrupted " Andrea Parri
2026-11-04 10:37 ` Andrea Parri [this message]
2026-11-04 10:37 ` [PATCH 4/4] seccomp: publish user notifications after copying them to userspace Andrea Parri
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=20261104103736.71956-4-parri.andrea@gmail.com \
--to=parri.andrea@gmail.com \
--cc=benquike@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=brads@mainlining.org \
--cc=brauner@kernel.org \
--cc=cwang@multikernel.io \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=rodrigo@kinvolk.io \
--cc=sargun@sargun.me \
--cc=shuah@kernel.org \
--cc=tycho@tycho.pizza \
--cc=wad@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®