From: Ulrich Drepper <drepper@redhat.com>
To: Neil Brown <neilb@suse.de>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] utimensat implementation
Date: Thu, 10 May 2007 11:26:36 -0700 [thread overview]
Message-ID: <464363DC.7060607@redhat.com> (raw)
In-Reply-To: <46315C61.30001@redhat.com>
Ulrich Drepper wrote:
> Neil Brown wrote:
>> Does it also specify how to find out what granularity is used by the
>> filesystem? I had a need for this just recently and couldn't see any
>> way to extract it.
>
> That's still on the table. We might end up with an fpathconf() solution.
OK, the pathconf()-based solution will most probably be in the next
POSIX spec.
Now, somebody has to provide a way to get to this information. The
kernel does not export it so far. Is it finally time to break down and
allow pathconf() and fpathconf() syscalls into the kernel?
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
next prev parent reply other threads:[~2007-05-10 18:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 22:49 [PATCH] utimensat implementation Ulrich Drepper
2007-04-26 23:25 ` Andrew Morton
2007-04-27 0:11 ` H. Peter Anvin
2007-04-27 0:55 ` Ulrich Drepper
2007-04-27 0:58 ` H. Peter Anvin
2007-04-27 1:04 ` Ulrich Drepper
2007-04-27 23:15 ` H. Peter Anvin
2007-04-27 23:05 ` David Lang
2007-04-27 23:30 ` Ulrich Drepper
2007-04-27 23:33 ` H. Peter Anvin
2007-04-27 0:54 ` Ulrich Drepper
2007-04-27 15:27 ` Updated utimensat test program Ulrich Drepper
2007-04-27 1:57 ` [PATCH] utimensat implementation Neil Brown
2007-04-27 2:13 ` Ulrich Drepper
2007-04-27 6:01 ` Neil Brown
2007-05-10 18:26 ` Ulrich Drepper [this message]
2007-05-10 18:52 ` Christoph Hellwig
2007-05-10 19:44 ` Ulrich Drepper
2007-05-13 21:02 ` Christoph Hellwig
2007-05-11 1:01 ` H. Peter Anvin
2007-05-11 2:14 ` Neil Brown
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=464363DC.7060607@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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