public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30515] _dl_find_object incorrectly returns 1 during early startup
Date: Fri, 07 Jul 2023 08:44:51 +0000 [thread overview]
Message-ID: <bug-30515-131-hcnBEBr6hN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30515-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30515
--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Florian Weimer <fw@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=1bcfe0f732066ae5336b252295591ebe7e51c301
commit 1bcfe0f732066ae5336b252295591ebe7e51c301
Author: Florian Weimer <fweimer@redhat.com>
Date: Fri Jul 7 10:11:26 2023 +0200
elf: _dl_find_object may return 1 during early startup (bug 30515)
Success is reported with a 0 return value, and failure is -1.
Enhance the kitchen sink test elf/tst-audit28 to cover
_dl_find_object as well.
Fixes commit 5d28a8962dcb ("elf: Add _dl_find_object function")
and bug 30515.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
Tested-by: Carlos O'Donell <carlos@redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-07 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 15:07 [Bug dynamic-link/30515] New: " fweimer at redhat dot com
2023-06-05 15:08 ` [Bug dynamic-link/30515] " fweimer at redhat dot com
2023-07-07 8:44 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-07 8:45 ` fweimer at redhat dot com
2023-07-07 9:13 ` cvs-commit at gcc dot gnu.org
2023-07-07 9:40 ` cvs-commit at gcc dot gnu.org
2023-07-07 10:12 ` cvs-commit at gcc dot gnu.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-30515-131-hcnBEBr6hN@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).