[lkml]   [2004]   [Oct]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 25/28] VFS: statfs(64) shouldn't follow last component symlink
    Hash: SHA1

    Christoph Hellwig wrote:
    > On Mon, Oct 25, 2004 at 10:51:11AM -0400, Mike Waychison wrote:
    >>Mount-related userspace tools will require the ability to detect whether what
    >>looks like a regular directory is actually a autofs trigger. To handle this,
    >>tools can statfs a given directory and check to see if statfs->f_type ==
    >>AUTOFSNG_SUPER_MAGIC before walking into the directory (and causing the a
    >>filesystem to automount).
    >>To make this happen, we cannot allow statfs to follow_link.
    >>NOTE: This may break any userspace that assumes it can statfs across a
    >>last-component symlink. I can't think of any real world breakage however, as
    >>mount(8) will drop the real path in /etc/mtab and /proc/mounts will always
    >>show the true path.
    > Which means it's vetoed. It's a big change in syscall semantics. And
    > propabably breaks SuS (for statvfs(3) which requires full symlink
    > resolution when it just refers to a path on the filesystem.

    Ya, I figured that would be the case. What do folks think about a

    - --
    Mike Waychison
    Sun Microsystems, Inc.
    1 (650) 352-5299 voice
    1 (416) 202-8336 voice

    NOTICE: The opinions expressed in this email are held by me,
    and may not represent the views of Sun Microsystems, Inc.
    Version: GnuPG v1.2.5 (GNU/Linux)
    Comment: Using GnuPG with Thunderbird -

    -----END PGP SIGNATURE-----
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:07    [W:0.022 / U:42.864 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site