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]

Date:	Sun, 22 Apr 2007 10:10:33 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	Andreas Gruenbacher <agruen@...e.de>
Cc:	Ulrich Drepper <drepper@...il.com>,
	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 Sat, Apr 21, 2007 at 09:04:06PM +0200, Andreas Gruenbacher wrote:
> > It is unspecified whether all members of the statvfs structure have
> > meaningful values on all file systems.
> 
> In my opinion, the advantage of not reporting bogus pathnames in /proc/mounts 
> by far outweighs the problems is sometimes causes for fstatvfs(). Anyone 
> relying on the information obtained from statvfs / fstatvfs is making false 
> assumptions anyway, and in "normal setups" as you called them, nothing 
> changes for fstatvfs and statvfs.

So what about stopping the flaming here and implementing real statvfs/
fstatvfs syscalls instead of these horrible hacks glibc has to do currently?
Using our kstatfs infrastructure that should be dirt simple.
arch/sparc64/solaris/fs.c already has a template of a statvfs syscall for
solaris, although we could probably improve a little on that.

-
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/