From: Christian Brauner <christian@brauner.io>
To: oleg@redhat.com, linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, tj@kernel.org, tglx@linutronix.de,
prsood@codeaurora.org, avagin@gmail.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] exit: make setting exit_state consistent
Date: Mon, 29 Jul 2019 18:30:27 +0200 [thread overview]
Message-ID: <20190729163025.4jc6d4nkdcdhve2k@brauner.io> (raw)
In-Reply-To: <20190729162757.22694-1-christian@brauner.io>
On Mon, Jul 29, 2019 at 06:27:57PM +0200, Christian Brauner wrote:
> Since commit [1] we unconditionally set exit_state to EXIT_ZOMBIE before
> calling into do_notify_parent(). This was done to eliminate a race when
> querying exit_state in do_notify_pidfd().
> Back then we decided to do the absolute minimal thing to fix this and
> not touch the rest of the exit_notify() function where exit_state is
> set.
> Since this fix has not caused any issues change the setting of
> exit_state to EXIT_DEAD in the autoreap case to account for the fact hat
> exit_state is set to EXIT_ZOMBIE unconditionally. This fix was planned
> but also explicitly requested in [2] and makes the whole code more
> consistent.
>
> /* References */
> [1]: b191d6491be6 ("pidfd: fix a poll race when setting exit_state")
> [2]: https://lore.kernel.org/lkml/CAHk-=wigcxGFR2szue4wavJtH5cYTTeNES=toUBVGsmX0rzX+g@mail.gmail.com
>
> Signed-off-by: Christian Brauner <christian@brauner.io>
> Cc: Oleg Nesterov <oleg@redhat.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
I plan on sending this together with a few other fixes later. (Assuming
the change here is correct of course.)
Christian
next prev parent reply other threads:[~2019-07-29 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 16:27 Christian Brauner
2019-07-29 16:30 ` Christian Brauner [this message]
2019-07-30 16:32 ` 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=20190729163025.4jc6d4nkdcdhve2k@brauner.io \
--to=christian@brauner.io \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=prsood@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--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
all inboxes | Powered by JetHome®