From: Linus Torvalds <torvalds@linux-foundation.org>
To: Eddy Wu <itseddy0402@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Security Officers <security@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
eddy_wu@trendmicro.com
Subject: Re: [PATCH] fork: fix copy_process(CLONE_PARENT) race with the exiting ->real_parent
Date: Sun, 8 Nov 2020 11:19:14 -0800 [thread overview]
Message-ID: <CAHk-=whjyOuO-xwov7UWidBOkWyZv84TVA18hBb01V-hiML+yg@mail.gmail.com> (raw)
In-Reply-To: <20201107064722.GA139215@arch-e3.localdomain>
On Fri, Nov 6, 2020 at 10:47 PM Eddy Wu <itseddy0402@gmail.com> wrote:
>
> current->group_leader->exit_signal may change during copy_process() if
> current->real_parent exits, move the assignment inside tasklist_lock to avoid
> the race.
Applied. Thanks,
Linus
prev parent reply other threads:[~2020-11-08 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 6:47 [PATCH] fork: fix copy_process(CLONE_PARENT) race with the exiting ->real_parent Eddy Wu
2020-11-08 19:19 ` Linus Torvalds [this message]
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='CAHk-=whjyOuO-xwov7UWidBOkWyZv84TVA18hBb01V-hiML+yg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=eddy_wu@trendmicro.com \
--cc=itseddy0402@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=security@kernel.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).