[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a36005b50704200815j30c95caele31536948343e29a@mail.gmail.com>
Date: Fri, 20 Apr 2007 08:15:54 -0700
From: "Ulrich Drepper" <drepper@...il.com>
To: "Andreas Gruenbacher" <agruen@...e.de>
Cc: "Alan Cox" <alan@...rguk.ukuu.org.uk>, jjohansen@...e.de,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org, chrisw@...s-sol.org,
"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: [d_path 0/7] Fixes to d_path: Respin
On 4/20/07, Andreas Gruenbacher <agruen@...e.de> wrote:
> Possibly for fstatfs(): fstatfs() has no way of looking up mount points per
> path name in /proc/mounts, and so it resorts to mapping from the numeric
> statfs->f_type to the filesystem name (e.g., "ext3"), looks up the first
> mount point with that name, and sets the statfs->f_flag flags based on that
> entry. This field may change from one arbitrary value to another.
What are you talking about? fstatfs is a syscall, we do nothing but
copying values around at userlevel.
statvfs on the other hand does use /proc/mounts. And it most
certainly does look at the mount point before looking at the
filesystem type.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists