From: AnonymeMeow <anonymemeow@gmail.com>
To: amir73il@gmail.com
Cc: brauner@kernel.org, jack@suse.cz, repnop@google.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
AnonymeMeow <anonymemeow@gmail.com>
Subject: [PATCH v3 0/2] fanotify: lift pidfd reporting restrictions
Date: Sat, 30 May 2026 09:37:30 +0800 [thread overview]
Message-ID: <20260530013732.50811-1-anonymemeow@gmail.com> (raw)
The pidfd API now supports pidfds for tasks that are not thread group leaders,
but fanotify has not caught up yet. This patch set lifts that restriction and
allows fanotify to report pidfds referring the event-generating thread.
Additionally, this patch set drops the pid_has_task() check before the
pidfd_prepare() call, allowing fanotify to hand out pidfds for reaped tasks,
as suggested by Christian.
Link: https://lore.kernel.org/lkml/20260528-schmuckvoll-heilen-garen-be77b4208671@brauner/
changes since v2:
- Split the two independent changes into separate patches.
v2: https://lore.kernel.org/lkml/20260529020035.17477-1-anonymemeow@gmail.com/
AnonymeMeow (2):
fanotify: report thread pidfds for FAN_REPORT_TID
fanotify: allow reporting pidfds for reaped tasks
fs/notify/fanotify/fanotify_user.c | 33 +++++++-----------------------
1 file changed, 7 insertions(+), 26 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-30 1:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 1:37 AnonymeMeow [this message]
2026-05-30 1:37 ` [PATCH v3 1/2] fanotify: report thread pidfds for FAN_REPORT_TID AnonymeMeow
2026-05-30 13:51 ` Amir Goldstein
2026-05-30 1:37 ` [PATCH v3 2/2] fanotify: allow reporting pidfds for reaped tasks AnonymeMeow
2026-05-30 13:51 ` Amir Goldstein
2026-05-30 10:51 ` [RFC][PATCH] fanotify: register event pid for pidfd reporting AnonymeMeow
2026-06-01 15:24 ` Jan Kara
2026-06-02 13:50 ` Christian Brauner
2026-06-08 9:27 ` Jan Kara
2026-06-08 12:30 ` Jan Kara
2026-06-10 7:33 ` Christian Brauner
2026-06-08 10:53 ` [PATCH v3 0/2] fanotify: lift pidfd reporting restrictions Jan Kara
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=20260530013732.50811-1-anonymemeow@gmail.com \
--to=anonymemeow@gmail.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=repnop@google.com \
/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®