From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: GLIBC Devel <libc-alpha@sourceware.org>,
"Carlos O'Donell" <carlos@redhat.com>
Subject: Re: [PATCH] elf: Self-dlopen failure with explict loader invocation [BZ #24900]
Date: Mon, 12 Aug 2019 19:41:00 -0000 [thread overview]
Message-ID: <CALoOobMNy15qo90bd27svPM8+6Z14hV6B4in3tkq1J=xLmGgNw@mail.gmail.com> (raw)
In-Reply-To: <87ftm6mbyw.fsf@oldenburg2.str.redhat.com>
On Mon, Aug 12, 2019 at 12:15 PM Florian Weimer <fweimer@redhat.com> wrote:
> 2019-08-12 Florian Weimer <fweimer@redhat.com>
>
> [BZ #24900]
> * elf/dl-object.c (_dl_new_object): Do not store pathnames in the
...
> +++ b/elf/tst-dlopen-aout.c
> @@ -1,7 +1,8 @@
> -/* Test case for BZ #16634.
> +/* Test case for BZ #16634 and BZ#24899.
Should this be 24900?
BZ#24899 doesn't appear to have anything to do with the dynamic loader.
The patch looks good to me. Thanks!
--
Paul Pluzhnikov
next prev parent reply other threads:[~2019-08-12 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 19:16 Florian Weimer
2019-08-12 19:41 ` Paul Pluzhnikov [this message]
2019-08-12 19:52 ` Florian Weimer
2019-08-15 11:47 ` Carlos O'Donell
2019-08-15 12:38 ` Florian Weimer
2019-08-15 16:10 ` Carlos O'Donell
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='CALoOobMNy15qo90bd27svPM8+6Z14hV6B4in3tkq1J=xLmGgNw@mail.gmail.com' \
--to=ppluzhnikov@google.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.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).