qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 1813307] Re: util/path.c/follow_path() does not handle "/" well


From: Thomas Huth
Subject: [Bug 1813307] Re: util/path.c/follow_path() does not handle "/" well
Date: Wed, 05 May 2021 11:11:01 -0000

This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:

 https://gitlab.com/qemu-project/qemu/-/issues/162


** Changed in: qemu
       Status: New => Expired

** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #162
   https://gitlab.com/qemu-project/qemu/-/issues/162

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1813307

Title:
  util/path.c/follow_path() does not handle "/" well

Status in QEMU:
  Expired

Bug description:
  Hello,

  I noticed that qemu does not handle "/" very well in follow_path().

  Specifically, I was trying to run gdbserver under qemu, and it failed
  inside its implementation of __getcwd.

  Indeed it does something like
    if (__lstat ("/", &st) < 0)
  .....
  and then loops from current dir toward the top using lstat("..")

  On qemu side, lstat forwards the request to follow_path() in util/path.c, and 
when passed "/", it returns the path in QEMU_LD_PREFIX (which was the top of my 
sysroot).
  OTHT, the series of lstat("..") finally reaches the real device root because 
it's not recognized as "/" in follow_path(), so this is inconsistent and 
__getcwd fails.

  I suppose there's a good reason for returning QEMU_LD_PREFIX when
  asking for "/", but why is it so?

  If there's no good reason, maybe the behaviour could be changed to map
  "/" to "/" ?

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1813307/+subscriptions



reply via email to

[Prev in Thread] Current Thread [Next in Thread]