From: Laurent Vivier <Laurent@vivier.eu>
To: qemu-devel@nongnu.org
Subject: [Bug 1245703] Re: LD_PREFIX option reads directories recursively in an endless loop
Date: Mon, 03 Feb 2020 09:17:17 -0000 [thread overview]
Message-ID: <158072143774.18982.9247639324642037332.malone@gac.canonical.com> (raw)
In-Reply-To: 20131028231528.17025.5795.malonedeb@chaenomeles.canonical.com
Fixed by in 4.1.0 by:
f3a8bdc1d5b2 ("util/path: Do not cache all filenames at startup")
** Changed in: qemu
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1245703
Title:
LD_PREFIX option reads directories recursively in an endless loop
Status in QEMU:
Fix Released
Status in qemu package in Debian:
Fix Released
Bug description:
If I run qemu user emulation with -L /path/to/my/sysroot/ in which
also the proc and dev filesystem is mounted QEMU eats my memory until
it gets killed by the kernel.
According to the strace output it follows the symbolic links in the
proc filesystem running forever in a recursive loop.
The easiest solution would be to add in the function "add_dir_maybe"
in the file util/path.c an additional check for symbolic links that it
don't follow them.
Also I don't really understand the need of doing this. A lot of
ressources are wasted everytime QEMU-user is started just by having
the directory structure in memory. In my case this are more than 20000
entries which QEMU is loading every time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1245703/+subscriptions
prev parent reply other threads:[~2020-02-03 9:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 23:15 [Qemu-devel] [Bug 1245703] [NEW] LD_PREFIX option reads directories recursively in an endless loop Sebastian Macke
2013-10-28 23:24 ` Peter Maydell
2013-10-29 0:44 ` [Qemu-devel] [Bug 1245703] " Sebastian Macke
2013-12-08 12:45 ` Antonis Kanouras
2013-12-08 12:57 ` Antonis Kanouras
2013-12-08 13:59 ` Bug Watch Updater
2015-03-26 21:37 ` Ross Burton
2015-03-26 22:37 ` Peter Maydell
2015-03-27 15:45 ` Ross Burton
2017-11-07 17:19 ` Peter Maydell
2017-11-08 9:12 ` Richard Henderson
2018-04-06 5:53 ` Bug Watch Updater
2020-02-03 9:17 ` Laurent Vivier [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=158072143774.18982.9247639324642037332.malone@gac.canonical.com \
--to=laurent@vivier.eu \
--cc=1245703@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.