From: Dodji Seketeli <dodji@seketeli.org>
To: Matthias Maennich <maennich@google.com>
Cc: libabigail@sourceware.org, gprocida@google.com,
kernel-team@android.com
Subject: Re: [PATCH] tools-utils: Do not skip symbolic links when analyzing a linux tree
Date: Wed, 01 Sep 2021 10:53:04 +0200 [thread overview]
Message-ID: <8735qohe33.fsf@seketeli.org> (raw)
In-Reply-To: <20210824213012.2486940-1-maennich@google.com> (Matthias Maennich's message of "Tue, 24 Aug 2021 22:30:12 +0100")
Hello Matthias,
Matthias Maennich <maennich@google.com> a écrit:
> For various reasons, (parts of) a linux kernel tree containing vmlinux
> and kernel modules might be organized using symbolic links. One reason
> is that those binaries physically reside on a different storage and are
> linked into place. To support such scenarios by allowing to traverse
> symbolic links when discovering linux kernel binaries.
>
> I could not see a reason why this was disabled in the first place.
> Ignoring symbolic links had been the default since the inception of the
> kernel mode.
Following symbolic link is disabled because there can be cases where the
link points to a directory of the kernel tree, causing cycles in the
tree. In that case, fts_read can return the same file several times.
I seem to remember that it had noticeable performance impacts on the
tests I did with our kernels.
So to support symbolic link, we'd need to properly handle (avoid?) those
cycles, probably by taking into account the FTS_DC bit of the
FTSENT::fts_info data member. I haven't looked into it in details,
though.
Have you seen the same think in those cases?
Thanks.
[...]
--
Dodji
prev parent reply other threads:[~2021-09-08 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 21:30 Matthias Maennich
2021-09-01 8:53 ` Dodji Seketeli [this message]
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=8735qohe33.fsf@seketeli.org \
--to=dodji@seketeli.org \
--cc=gprocida@google.com \
--cc=kernel-team@android.com \
--cc=libabigail@sourceware.org \
--cc=maennich@google.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).