From: Christian Brauner <christian@brauner.io>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, oleg@redhat.com, joel@joelfernandes.org
Subject: [GIT PULL] pidfd fixes
Date: Tue, 30 Jul 2019 21:04:37 +0200 [thread overview]
Message-ID: <20190730190437.19004-1-christian@brauner.io> (raw)
Hi Linus,
This makes setting the exit_state in exit_notify() consistent after fixing
the pidfd polling race pre-rc1. Related to the race fix, this adds a
WARN_ON() to do_notify_pidfd() to catch any future exit_state races.
Last, this removes an obsolete comment from the pidfd tests.
The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:
Linux 5.3-rc2 (2019-07-28 12:47:02 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux tags/for-linus-20190730
for you to fetch changes up to 30b692d3b390c6fe78a5064be0c4bbd44a41be59:
exit: make setting exit_state consistent (2019-07-30 19:57:14 +0200)
Please consider pulling from the signed for-linus-20190730 tag.
Thanks!
Christian
----------------------------------------------------------------
for-linus-20190730
----------------------------------------------------------------
Christian Brauner (2):
pidfd: remove obsolete comments from test
exit: make setting exit_state consistent
Joel Fernandes (Google) (1):
pidfd: Add warning if exit_state is 0 during notification
kernel/exit.c | 5 +++--
kernel/signal.c | 1 +
tools/testing/selftests/pidfd/pidfd_test.c | 6 +-----
3 files changed, 5 insertions(+), 7 deletions(-)
next reply other threads:[~2019-07-30 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 19:04 Christian Brauner [this message]
2019-07-30 20:40 ` [GIT PULL] pidfd fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-07-22 14:22 Christian Brauner
2019-07-22 16:27 ` Linus Torvalds
2019-07-22 16:39 ` Christian Brauner
2019-07-23 10:12 ` Oleg Nesterov
2019-07-23 10:25 ` Christian Brauner
2019-07-22 16:40 ` pr-tracker-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=20190730190437.19004-1-christian@brauner.io \
--to=christian@brauner.io \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).