From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Andreas Fink <finkandreas@web.de>
Cc: libc-help <libc-help@sourceware.org>
Subject: Re: segmentation fault with glibc-2.34
Date: Fri, 3 Dec 2021 11:55:12 -0300 [thread overview]
Message-ID: <CAMXh4bVBP5EU+1Zi4fK+=GHr0Miytjb-_J3+336t8i=J+TnL2A@mail.gmail.com> (raw)
In-Reply-To: <20211203143805.04797c96@anfink-laptop>
On Fri, Dec 3, 2021 at 10:38 AM Andreas Fink via Libc-help
<libc-help@sourceware.org> wrote:
>
> Hello,
> I have observed a crash in firefox with glibc-2.34 and have found a
> small reproducer.
> Is the sigsys signal handler valid? If yes, then there is a bug in
> glibc-2.34.
> If it is invalid to set the result in the context, I think the firefox
> sandbox is doing dodgy things.
>
> gcc test.c -lseccomp
> strace ./a.out
The seccomp filter *explicitly* blocks newfstatat, which might be used
by getpwuid.
>
> This test reproducer does not segfault with 2.33 (it gives a
> "Permission denied")
>
> Cheers
> Andreas
next prev parent reply other threads:[~2021-12-03 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 13:38 Andreas Fink
2021-12-03 14:55 ` Adhemerval Zanella [this message]
2021-12-03 15:02 ` Florian Weimer
2021-12-03 15:15 ` Adhemerval Zanella
2021-12-03 15:03 ` Adhemerval Zanella
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='CAMXh4bVBP5EU+1Zi4fK+=GHr0Miytjb-_J3+336t8i=J+TnL2A@mail.gmail.com' \
--to=adhemerval.zanella@linaro.org \
--cc=finkandreas@web.de \
--cc=libc-help@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).