From: Oleg Nesterov <oleg@redhat.com>
To: Andrei Vagin <avagin@google.com>
Cc: Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org,
Tycho Andersen <tandersen@netflix.com>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH 1/4] seccomp: interrupt SECCOMP_IOCTL_NOTIF_RECV when all users have exited
Date: Fri, 28 Jun 2024 08:52:05 +0200 [thread overview]
Message-ID: <20240628065204.GA29300@redhat.com> (raw)
In-Reply-To: <20240628021014.231976-2-avagin@google.com>
On 06/28, Andrei Vagin wrote:
>
> SECCOMP_IOCTL_NOTIF_RECV promptly returns when a seccomp filter becomes
> unused, as a filter without users can't trigger any events.
>
> Previously, event listeners had to rely on epoll to detect when all
> processes had exited.
>
> The change is based on the 'commit 99cdb8b9a573 ("seccomp: notify about
> unused filter")' which implemented (E)POLLHUP notifications.
>
> Reviewed-by: Christian Brauner <brauner@kernel.org>
> Signed-off-by: Andrei Vagin <avagin@google.com>
> ---
> kernel/seccomp.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
next prev parent reply other threads:[~2024-06-28 6:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 2:10 [PATCH 0/4 v3] seccomp: improve handling of SECCOMP_IOCTL_NOTIF_RECV Andrei Vagin
2024-06-28 2:10 ` [PATCH 1/4] seccomp: interrupt SECCOMP_IOCTL_NOTIF_RECV when all users have exited Andrei Vagin
2024-06-28 6:52 ` Oleg Nesterov [this message]
2024-06-28 2:10 ` [PATCH 2/4] seccomp: release task filters when the task exits Andrei Vagin
2024-06-28 2:10 ` [PATCH 3/4] selftests/seccomp: add test for NOTIF_RECV and unused filters Andrei Vagin
2024-06-28 2:10 ` [PATCH 4/4] selftests/seccomp: check that a zombie leader doesn't affect others Andrei Vagin
2024-06-28 16:38 ` [PATCH 0/4 v3] seccomp: improve handling of SECCOMP_IOCTL_NOTIF_RECV Kees Cook
2024-07-02 19:33 ` Tycho Andersen
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=20240628065204.GA29300@redhat.com \
--to=oleg@redhat.com \
--cc=avagin@google.com \
--cc=brauner@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=tandersen@netflix.com \
--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