From: Florian Weimer <fweimer@redhat.com>
To: Gian-Carlo Pascutto <gpascutto@mozilla.com>
Cc: "Szabolcs Nagy" <szabolcs.nagy@arm.com>,
mathieu.desnoyers@efficios.com, libc-alpha@sourceware.org,
"Christian Brauner" <christian.brauner@ubuntu.com>,
"Jed Davis" <jld@mozilla.com>,
"Emilio Cobos Álvarez" <ealvarez@mozilla.com>,
"Rich Felker" <dalias@libc.org>
Subject: Re: glibc 2.32 rseq support incompatible with Firefox sandbox
Date: Thu, 09 Jul 2020 20:15:49 +0200 [thread overview]
Message-ID: <87d0545zca.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CAMqpMh4k2tAMOqEkHyt1HFRx8wsgUZbroLUenta40n5+8u9hiw@mail.gmail.com> (Gian-Carlo Pascutto's message of "Thu, 9 Jul 2020 20:10:10 +0200")
* Gian-Carlo Pascutto:
> If all we need to do here is allow rseq, then it's not really a
> problem. If it's a more fundamental issue with the signal blocking,
> we'll need to figure out a workaround until sandboxed browsers can add
> support for and add the entirely new seccomp implementation.
rseq and rt_sigprocmask are the only new system call after clone in
glibc 2.32. rt_sigprocmask should be fine, so only rseq needs to be
permitted. It would be be best not to deny rseq on specific threads if
it has already succeeded on the main thread.
Thanks,
Florian
next prev parent reply other threads:[~2020-07-09 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 15:03 Florian Weimer
2020-07-09 15:19 ` H.J. Lu
2020-07-09 15:29 ` Florian Weimer
2020-07-09 15:59 ` Mathieu Desnoyers
2020-07-09 16:34 ` Szabolcs Nagy
2020-07-09 18:10 ` Gian-Carlo Pascutto
2020-07-09 18:15 ` Florian Weimer [this message]
2020-07-10 3:16 ` Carlos O'Donell
2020-07-10 8:28 ` Florian Weimer
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=87d0545zca.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=christian.brauner@ubuntu.com \
--cc=dalias@libc.org \
--cc=ealvarez@mozilla.com \
--cc=gpascutto@mozilla.com \
--cc=jld@mozilla.com \
--cc=libc-alpha@sourceware.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=szabolcs.nagy@arm.com \
/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).