[Bug 482978] Re: ls can't cross mounted filesystems with ".." in path

[Dave Gilbert]

Hi Philip,
   Did you get to the bottom of this?  This is almost certainly not coreutils - I'm fairly sure pretty much everything in that path walk is done in the kernel.

It's unlikely to be the fsck either.

Have you been able to repeat it?

Dave

** Changed in: coreutils (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/482978

Title:
  ls can't cross mounted filesystems with ".." in path

Status in “coreutils” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: coreutils

  I suspect the real problem is in something ls uses - hopefully
  coreutils developers will be in a better position to determine the
  underlying cause.

  I'm using crypto/lvm2 and have root mounted on one lvm ext4 partition and /v3c mounted on an ext3 lvm partition.
  If I do
      $ ls /usr/share/bison/../../../v3c/dev/autobook/parse/build/../v3c/flexx/tests/bison_calc.m4
  I get "No such file or directory".
  But with
      $ ls /v3c/dev/autobook/parse/build/../v3c/flexx/tests/bison_calc.m4
  the file gets listed.
  /bin/ls isn't the only program to exhibit this behaviour - m4 is doing the same thing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/482978/+subscriptions