From: Florian Weimer <fweimer@redhat.com>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: clone3: CLONE_CLEAR_SIGHAND v5.5
Date: Wed, 04 Dec 2019 13:45:00 -0000 [thread overview]
Message-ID: <877e3cp5l8.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20191204131616.3kzhpi5rnlxrxrbb@wittgenstein> (Christian Brauner's message of "Wed, 4 Dec 2019 14:16:16 +0100")
* Christian Brauner:
> On Tue, Oct 08, 2019 at 03:44:17PM +0200, Christian Brauner wrote:
>> Reset all signal handlers of the child not set to SIG_IGN to SIG_DFL.
>> Mutually exclusive with CLONE_SIGHAND to not disturb other threads
>> signal handler.
>
> Hey,
>
> Just a heads up that Linus pulled CLONE_CLEAR_SIGHAND with other changes
> for v5.5:
>
> clone3: add CLONE_CLEAR_SIGHAND:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b612e5df4587c934bd056bf05f4a1deca4de4f75
>
> tests: test CLONE_CLEAR_SIGHAND
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de5287235631cc561716d85f984614ef9598a5cc
Very nice, thanks.
Florian
prev parent reply other threads:[~2019-12-04 13:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 13:44 [PATCH] [GLIBC RFC] clone3: add CLONE3_RESET_SIGHAND Christian Brauner
2019-10-08 14:14 ` Christian Brauner
2019-10-08 14:20 ` Adhemerval Zanella
2019-10-09 10:48 ` Christian Brauner
2019-10-09 11:04 ` Florian Weimer
2019-10-09 11:12 ` Christian Brauner
2019-10-09 11:56 ` Florian Weimer
2019-10-09 11:58 ` Christian Brauner
2019-10-09 12:01 ` Florian Weimer
2019-10-09 13:33 ` Christian Brauner
2019-10-10 10:51 ` Christian Brauner
2019-10-10 14:49 ` Florian Weimer
2019-10-11 10:47 ` Christian Brauner
2019-10-09 11:14 ` Dmitry V. Levin
2019-12-04 13:16 ` clone3: CLONE_CLEAR_SIGHAND v5.5 Christian Brauner
2019-12-04 13:45 ` Florian Weimer [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=877e3cp5l8.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=christian.brauner@ubuntu.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).