From: Oleg Nesterov <oleg@redhat.com>
To: Christian Brauner <brauner@kernel.org>,
David Laight <david.laight.linux@gmail.com>,
Jeff Layton <jlayton@kernel.org>,
Mingyu Wang <25181214217@stu.xidian.edu.cn>
Cc: alex.aring@gmail.com, jack@suse.cz, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] add pid::tasks_lock to fix send_sigio() and send_sigurg()
Date: Sat, 17 Oct 2026 17:49:15 +0200 [thread overview]
Message-ID: <atOY-5ZjqVTQw2JE@redhat.com> (raw)
Not for inclusion yet, just RFC. In particular, I'd like to have
a review from sashiko, I am sure I missed something ;)
Only compile tested, the changelog is obviously incomplete,
__change_pid() should die after this change, etc.
And. I am still not sure that the new lock should be per pid, perhaps
a simple global lock which aligns with tasklist makes more sense, it
should not be contended too much.
Please comment.
Oleg.
fs/fcntl.c | 4 ++++
include/linux/pid.h | 1 +
kernel/pid.c | 24 +++++++++++++++++++-----
3 files changed, 24 insertions(+), 5 deletions(-)
next reply other threads:[~2026-10-17 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 15:49 Oleg Nesterov [this message]
2026-10-17 15:49 ` [PATCH 1/1] add pid::tasks_lock to fix send_sigio() and send_sigurg() Oleg Nesterov
2026-10-17 16:10 ` [PATCH 0/1] " Oleg Nesterov
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=atOY-5ZjqVTQw2JE@redhat.com \
--to=oleg@redhat.com \
--cc=25181214217@stu.xidian.edu.cn \
--cc=alex.aring@gmail.com \
--cc=brauner@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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