From: Eugene Syromiatnikov <esyr@redhat.com>
To: linux-kernel@vger.kernel.org,
Christian Brauner <christian@brauner.io>,
Oleg Nesterov <oleg@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
"Dmitry V. Levin" <ldv@altlinux.org>,
Eric Biederman <ebiederm@xmission.com>
Subject: [PATCH v3] fork: check exit_signal passed in clone3() call
Date: Wed, 11 Sep 2019 18:45:27 +0100 [thread overview]
Message-ID: <cover.1568223594.git.esyr@redhat.com> (raw)
Hello.
As was agreed[1][2], clone3 should fail if the provided exit_signal
value fails valid_signal() check, hence the new version.
Changees since v2[3][4]:
- Rewrite the check to check exit_signal against valid_signal().
Changes since v1[5]:
- Check changed to comparison against negated CSIGNAL to address
the bug reported by Oleg[6].
- Added a comment to _do_fork that exit_signal has to be checked
by the caller.
[1] https://lkml.org/lkml/2019/9/11/503
[2] https://lkml.org/lkml/2019/9/11/518
[3] https://lkml.org/lkml/2019/9/10/764
[4] https://lkml.org/lkml/2019/9/10/765
[5] https://lkml.org/lkml/2019/9/10/411
[6] https://lkml.org/lkml/2019/9/10/467
Eugene Syromiatnikov (1):
fork: check exit_signal passed in clone3() call
kernel/fork.c | 11 +++++++++++
1 file changed, 11 insertions(+)
--
2.1.4
next reply other threads:[~2019-09-11 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 17:45 Eugene Syromiatnikov [this message]
2019-09-11 17:45 ` [PATCH v3] fork: check exit_signal passed in clone3() call Eugene Syromiatnikov
2019-09-12 16:51 ` Oleg Nesterov
2019-09-13 11:40 ` Christian Brauner
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=cover.1568223594.git.esyr@redhat.com \
--to=esyr@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=christian@brauner.io \
--cc=ebiederm@xmission.com \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.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).