public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ludo at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/26634] ld.so stats raw file names, bypassing the audit module
Date: Thu, 24 Sep 2020 13:50:36 +0000 [thread overview]
Message-ID: <bug-26634-131-rjXHMZnlNa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26634-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26634
--- Comment #5 from Ludovic Courtès <ludo at gnu dot org> ---
(In reply to Florian Weimer from comment #4)
> Sorry, since the search path contains only the name without /PREFIX, probing
> without /PREFIX seems like the right thing to do to me. What am I missing?
'open_verify' checks /PREFIX/xyz/libfoo.so and returns -1. Then the caller
stats /xyz, determines that it's ENOENT, and marks the entry as nonexisting.
This is inconsistent: /PREFIX/xyz may well exist and thus, had we statted it,
we would not have marked the entry as nonexisting.
Does that make sense?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-24 13:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 21:44 [Bug dynamic-link/26634] New: " ludo at gnu dot org
2020-09-18 23:55 ` [Bug dynamic-link/26634] " mark at klomp dot org
2020-09-24 9:54 ` ludo at gnu dot org
2020-09-24 10:29 ` fweimer at redhat dot com
2020-09-24 13:31 ` ludo at gnu dot org
2020-09-24 13:35 ` fweimer at redhat dot com
2020-09-24 13:50 ` ludo at gnu dot org [this message]
2020-09-24 13:56 ` fweimer at redhat dot com
2020-09-24 14:11 ` ludo at gnu dot org
2020-09-24 14:14 ` fweimer at redhat dot com
2020-09-24 14:37 ` ludo at gnu dot org
2020-09-24 14:39 ` fweimer at redhat dot com
2020-09-24 15:01 ` ludo at gnu dot org
2020-09-24 15:04 ` fweimer at redhat dot com
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-26634-131-rjXHMZnlNa@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).