linux-kernel - Re: [d_path 0/7] Fixes to d

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200704201721.29825.agruen@suse.de>
Date:	Fri, 20 Apr 2007 17:21:29 +0200
From:	Andreas Gruenbacher <agruen@...e.de>
To:	"Ulrich Drepper" <drepper@...il.com>
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 Friday 20 April 2007 17:15, Ulrich Drepper wrote:
> 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.

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

Thanks,
Andreas
-
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/