From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ulrich Drepper Subject: Re: [rfc] new stat*fs-like syscall? Date: Fri, 25 Jun 2010 10:52:05 -0700 Message-ID: References: <20100624131455.GA10441@laptop> <20100625040156.GQ10441@laptop> <1A529206-98C4-4A88-A2CA-18522D4D631D@dilger.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Nick Piggin , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Al Viro , Ulrich Drepper , Linus Torvalds To: Andreas Dilger Return-path: In-Reply-To: <1A529206-98C4-4A88-A2CA-18522D4D631D@dilger.ca> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, Jun 25, 2010 at 10:47, Andreas Dilger wrote= : > SUSv2 only defines the flags ST_RDONLY and ST_NOSUID, and this is als= o what is documented in the Linux/BSD/OSX statvfs(3) man page. =C2=A0Ac= cording to the Solaris statvfs(3) man page I found it additionally defi= nes: > > ST_NOTRUNC =C2=A0 0x04 =C2=A0 =C2=A0/* does not truncate file names l= onger than > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0NAME_MAX */ glibc supports many more flags. SuS of course has to restrict itself, 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.