public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nss/28752] Segfault in getpwuid when stat fails
Date: Thu, 09 Jun 2022 05:35:22 +0000 [thread overview]
Message-ID: <bug-28752-131-02XeM0hI4x@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28752-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28752
--- Comment #4 from Sam James <sam at gentoo dot org> ---
(In reply to Sam James from comment #3)
> Fixed in master with 3fdf0a205b622e40fa7e3c4ed1e4ed4d5c6c5380 and
> ace9e3edbca62d978b1e8f392d8a5d78500272d9.
>
Sorry, thought it'd linkify:
commit ace9e3edbca62d978b1e8f392d8a5d78500272d9 (origin/master, origin/HEAD,
master)
Author: Sam James <sam@gentoo.org>
Date: Sun Jun 5 04:57:10 2022 +0100
nss: handle stat failure in check_reload_and_get (BZ #28752)
Skip the chroot test if the database isn't loaded
correctly (because the chroot test uses some
existing DB state).
The __stat64_time64 -> fstatat call can fail if
running under an (aggressive) seccomp filter,
like Firefox seems to use.
This manifested in a crash when using glib built
with FAM support with such a Firefox build.
Suggested-by: DJ Delorie <dj@redhat.com>
Signed-off-by: Sam James <sam@gentoo.org>
Reviewed-by: DJ Delorie <dj@redhat.com>
commit 3fdf0a205b622e40fa7e3c4ed1e4ed4d5c6c5380
Author: Sam James <sam@gentoo.org>
Date: Sun Jun 5 04:57:09 2022 +0100
nss: add assert to DB_LOOKUP_FCT (BZ #28752)
It's interesting if we have a null action list,
so an assert is worthwhile.
Suggested-by: DJ Delorie <dj@redhat.com>
Signed-off-by: Sam James <sam@gentoo.org>
Reviewed-by: DJ Delorie <dj@redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-09 5:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 18:30 [Bug nss/28752] New: " sam at gentoo dot org
2022-01-07 9:56 ` [Bug nss/28752] " fweimer at redhat dot com
2022-03-14 17:04 ` sam at gentoo dot org
2022-05-19 12:34 ` fweimer at redhat dot com
2022-06-09 5:34 ` sam at gentoo dot org
2022-06-09 5:35 ` sam at gentoo dot org [this message]
2022-06-19 2:18 ` sam at gentoo dot org
2022-06-19 2:19 ` sam at gentoo dot org
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=bug-28752-131-02XeM0hI4x@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).