From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Ulrich Drepper" Subject: Re: [d_path 0/7] Fixes to d_path: Respin Date: Fri, 20 Apr 2007 08:15:54 -0700 Message-ID: References: <20070412090809.917795000@suse.de> <20070419232303.300441585@schurl.suse.de> <20070420103008.15f37eec@the-village.bc.nu> <200704201345.09858.agruen@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Alan Cox" , jjohansen@suse.de, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org, chrisw@sous-sol.org, "Andrew Morton" To: "Andreas Gruenbacher" Return-path: Received: from nz-out-0506.google.com ([64.233.162.235]:39359 "EHLO nz-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2993259AbXDTPP4 (ORCPT ); Fri, 20 Apr 2007 11:15:56 -0400 Received: by nz-out-0506.google.com with SMTP id s1so777148nze for ; Fri, 20 Apr 2007 08:15:55 -0700 (PDT) In-Reply-To: <200704201345.09858.agruen@suse.de> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On 4/20/07, Andreas Gruenbacher 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.