From: Christoph Hellwig <hch@infradead.org>
To: Ulrich Drepper <drepper@gmail.com>
Cc: Andreas Dilger <adilger@dilger.ca>, Nick Piggin <npiggin@suse.de>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
Ulrich Drepper <drepper@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [rfc] new stat*fs-like syscall?
Date: Fri, 25 Jun 2010 14:45:04 -0400 [thread overview]
Message-ID: <20100625184504.GA11867@infradead.org> (raw)
In-Reply-To: <20100625181638.GA15227@infradead.org>
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?
next prev parent reply other threads:[~2010-06-25 18:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 13:14 [rfc] new stat*fs-like syscall? Nick Piggin
2010-06-24 14:03 ` Miklos Szeredi
2010-06-24 14:36 ` Nick Piggin
2010-06-24 14:08 ` Andy Lutomirski
2010-06-24 14:18 ` Miklos Szeredi
2010-06-24 14:37 ` Andrew Lutomirski
2010-06-24 14:48 ` Miklos Szeredi
2010-06-25 3:50 ` Nick Piggin
2010-06-24 23:06 ` Andreas Dilger
2010-06-25 6:37 ` Christoph Hellwig
2010-06-24 23:13 ` Andreas Dilger
2010-06-25 4:01 ` Nick Piggin
2010-06-25 4:33 ` Jeff Garzik
2010-06-25 17:47 ` Andreas Dilger
2010-06-25 17:52 ` Ulrich Drepper
2010-06-25 18:16 ` Christoph Hellwig
2010-06-25 18:45 ` Christoph Hellwig [this message]
2010-06-25 19:40 ` Ulrich Drepper
2010-06-26 5:53 ` J. R. Okajima
2010-06-26 9:35 ` Christoph Hellwig
2010-06-26 12:54 ` J. R. Okajima
2010-07-05 20:58 ` Brad Boyer
2010-07-05 23:31 ` J. R. Okajima
2010-07-06 0:45 ` Brad Boyer
2010-07-06 16:45 ` Linus Torvalds
2010-07-07 1:44 ` Christoph Hellwig
2010-07-07 2:28 ` Linus Torvalds
2010-06-26 14:49 ` Ulrich Drepper
2010-06-26 10:13 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100625184504.GA11867@infradead.org \
--to=hch@infradead.org \
--cc=adilger@dilger.ca \
--cc=drepper@gmail.com \
--cc=drepper@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).