| 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
| ||
|
Date: Fri, 25 Jun 2010 14:45:04 -0400 From: Christoph Hellwig <hch@...radead.org> To: Ulrich Drepper <drepper@...il.com> Cc: Andreas Dilger <adilger@...ger.ca>, Nick Piggin <npiggin@...e.de>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, Al Viro <viro@...iv.linux.org.uk>, Ulrich Drepper <drepper@...hat.com>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [rfc] new stat*fs-like syscall? On Fri, Jun 25, 2010 at 02:16:38PM -0400, Christoph Hellwig wrote: > On Fri, Jun 25, 2010 at 10:52:05AM -0700, Ulrich Drepper wrote: > > there are not that many flags which are portable and available on all > > the platforms. Look at /usr/include/bits/statvfs.h for what has to be > > supported and the values to use. If the values the kernel will use > > differ I'd have to (unnecessarily) convert the values. If some values > > are missing/not supported I still would have to use /proc/mounts and > > nothing is gained. > > I don't quite get what ST_WRITE is supposed to mean. All but that one > can be supported trivially. In addition ST_APPEND and ST_IMMUTABLE are rather puzzling. Do you really want these to mean if the file we call statfs on have the immutable/append only bits set? That is mixing two bits of stat information into statfs? -- 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