public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11149] ldconfig - auxiliary cache does not work properly with -r option
Date: Sat, 10 Apr 2010 13:43:00 -0000	[thread overview]
Message-ID: <20100410134312.5746.qmail@sourceware.org> (raw)
In-Reply-To: <20100108183822.11149.vas.gurevich@gmail.com>


------- Additional Comments From drepper at redhat dot com  2010-04-10 13:43 -------
(In reply to comment #4)
> Please, ask me if it is not enough. Thank you.

It isn't enough.  First, files named somelib are ignored because they don't look
like libraries.  I asked for the exact situation, not some general idea.

Second, even if I'm using a real library with its real name and then a link I
see no accesses outside the chroot:

I copied libc.so in a chroot tree and added libc.so.6 as a symlink.  The only
accesses to libc.so of

ldconfig -r $PWD/testroot

are:

lstat("$PWD/testroot/lib64/libc.so", {st_mode=S_IFREG|0775, st_size=9166760,
...}) = 0
open("$PWD/testroot/lib64/libc.so", O_RDONLY) = 4
stat("$PWD/testroot/lib64/libc.so.6", {st_mode=S_IFREG|0775, st_size=9166760,
...}) = 0
lstat("$PWD/testroot/lib64/libc.so.6", {st_mode=S_IFLNK|0777, st_size=7, ...}) = 0
readlink("$PWD/testroot/lib64/libc.so.6", "libc.so", 4096) = 7
lstat("$PWD/testroot/lib64/libc.so", {st_mode=S_IFREG|0775, st_size=9166760,
...}) = 0
lstat("$PWD/testroot/lib64/libc.so.6", {st_mode=S_IFLNK|0777, st_size=7, ...}) = 0
lstat("$PWD/testroot/lib64/libc.so.6", {st_mode=S_IFLNK|0777, st_size=7, ...}) = 0
readlink("$PWD/testroot/lib64/libc.so.6", "libc.so", 4096) = 7
lstat("$PWD/testroot/lib64/libc.so", {st_mode=S_IFREG|0775, st_size=9166760,
...}) = 0
stat("$PWD/testroot/lib64/libc.so", {st_mode=S_IFREG|0775, st_size=9166760,
...}) = 0
lstat("$PWD/testroot/lib64/libc.so", {st_mode=S_IFREG|0775, st_size=9166760,
...}) = 0
write(3, "libc.so.6\0/lib64/libc.so.6\0", 27) = 27

I have of course replace the real path with $PWD in the output.  But as you can
see there is no access outside the chroot.


Either provide _exact_ instructions for how to show the problem or close the
bug.  And make sure you're using current sources.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


http://sourceware.org/bugzilla/show_bug.cgi?id=11149

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2010-04-10 13:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08 18:38 [Bug libc/11149] New: " vas dot gurevich at gmail dot com
2010-04-05 18:28 ` [Bug libc/11149] " drepper at redhat dot com
2010-04-09 16:00 ` vas dot gurevich at gmail dot com
2010-04-09 16:34 ` drepper at redhat dot com
2010-04-09 17:26 ` vas dot gurevich at gmail dot com
2010-04-10 13:43 ` drepper at redhat dot com [this message]
2010-04-12 17:28 ` vas dot gurevich at gmail dot com
2010-05-03 21:05 ` drepper at redhat dot com
2010-05-25 19:24 ` vas dot gurevich at gmail dot com
2010-05-25 19:28 ` pasky at suse dot cz
2010-05-25 21:25 ` vas dot gurevich at gmail dot com
2010-05-27 19:29 ` vas dot gurevich at gmail dot com
2010-06-01  0:29 ` pasky at suse dot cz
2010-06-01  0:29 ` pasky at suse dot cz
2010-09-29 20:57 ` anssi dot hannula at iki dot fi
     [not found] <bug-11149-131@http.sourceware.org/bugzilla/>
2011-05-30  1:47 ` drepper.fsp at gmail dot com
2014-06-30 20:25 ` 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=20100410134312.5746.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).