Re: [d_path 0/7] Fixes to d_path: Respin

On 4/20/07, Andreas Gruenbacher <[email protected]> wrote:

Yes, that one, sorry. The values it obtains that way are not reliable.

Why should the mount point info together with the filesystem type not
be reliable?  You're trying to find an excuse to break tings, that
seems all there is.
-
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: Andreas Gruenbacher <[email protected]>

• References:
  • [AppArmor 00/41] AppArmor security module overview
    • From: [email protected]
  • Re: [d_path 0/7] Fixes to d_path: Respin
    • From: Andreas Gruenbacher <[email protected]>
  • Re: [d_path 0/7] Fixes to d_path: Respin
    • From: "Ulrich Drepper" <[email protected]>
  • Re: [d_path 0/7] Fixes to d_path: Respin
    • From: Andreas Gruenbacher <[email protected]>

• Prev by Date: Re: [d_path 0/7] Fixes to d_path: Respin
• Next by Date: Re: [PATCH 1/3] Char: mxser_new, fix recursive locking
• Previous by thread: Re: [d_path 0/7] Fixes to d_path: Respin
• Next by thread: Re: [d_path 0/7] Fixes to d_path: Respin
• 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]