[d_path 0/7] Fixes to d_path: Respin

On Tuesday 17 April 2007 19:21, Alan Cox wrote:
> Can you prove no existing application on the planet relies on the
> existing behaviour ? Actually more limited but sane as a test would be
> "Can you prove that the glibc behaviour visible to applications does not
> change"

As far as I can see, glibc internally looks at /proc/mounts (or else mtab) to
find out where tmpfs is mounted for opening files there, and to look up
filesystem information for statfs(), while accessing that path, too. Fstatfs()
also looks into the same files, but it only matches by filesystem type, so this
is only a very unreliable heuristic, anyway.

So judging from that, glibc users should be fine.

> I disagree - firstly because of not breaking stuff, and secondly because
> it separates two discussions - merging AppArmor being one of them , and
> the correct behaviour for getcwd & /proc/mounts being the other.

I agree with the separation of discussion argument. Here are patches that
change getcwd() and /proc/mounts independent of the changes that AppArmor
depends on.

Thanks for your feedback!

Andreas

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [d_path 0/7] Fixes to d_path: Respin
    • From: Alan Cox <[email protected]>
  • [d_path 2/7] Make d_path() consistent across mount operations
    • From: Andreas Gruenbacher <[email protected]>
  • [d_path 4/7] Make getcwd() only return valid paths
    • From: Andreas Gruenbacher <[email protected]>
  • [d_path 5/7] Remove duplicate proc code
    • From: Andreas Gruenbacher <[email protected]>
  • [d_path 3/7] Add d_namespace_path() to compute namespace relative pathnames
    • From: Andreas Gruenbacher <[email protected]>
  • [d_path 1/7] Fix __d_path() for lazy unmounts and make it unambiguous
    • From: Andreas Gruenbacher <[email protected]>
  • [d_path 7/7] Distinguish between connected and disconnected paths in d_path()
    • From: Andreas Gruenbacher <[email protected]>
  • [d_path 6/7] Filter out disconnected paths from /proc/mounts
    • From: Andreas Gruenbacher <[email protected]>

• References:
  • [AppArmor 00/41] AppArmor security module overview
    • From: [email protected]
  • Re: [AppArmor 31/41] Fix __d_path() for lazy unmounts and make it unambiguous; exclude unreachable mount points from /proc/mounts
    • From: Andreas Gruenbacher <[email protected]>
  • Re: [AppArmor 31/41] Fix __d_path() for lazy unmounts and make it unambiguous; exclude unreachable mount points from /proc/mounts
    • From: Alan Cox <[email protected]>

• Prev by Date: [d_path 4/7] Make getcwd() only return valid paths
• Next by Date: [d_path 2/7] Make d_path() consistent across mount operations
• Previous by thread: Re: [AppArmor 31/41] Fix __d_path() for lazy unmounts and make it unambiguous; exclude unreachable mount points from /proc/mounts
• Next by thread: [d_path 6/7] Filter out disconnected paths from /proc/mounts
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]