From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Andi Kleen <ak@suse.de>,
eggert@twinsun.com, linux-kernel@vger.kernel.org
Subject: Re: nanosecond file timestamp resolution in filesystems, GNU make, etc.
Date: Mon, 28 Oct 2002 15:13:09 +0000 [thread overview]
Message-ID: <20021028151309.GB16546@bjl1.asuk.net> (raw)
In-Reply-To: <Pine.GSO.3.96.1021028152012.977D-100000@delta.ds2.pg.gda.pl>
Maciej W. Rozycki wrote:
> > It's impossible. There is no space left in struct stat64
> > And adding a new syscall just for that would be severe overkill.
>
> Well, possibly more stuff could benefit from new stat syscalls, like a
> st_gen member for inode generations. And as someone suggested, a version
> number or a length could be specified by the calls this time to permit
> less disturbing expansion in the future.
It's already there. The kernel stat64() syscall has a flags argument,
which is unused at the moment. I presume it's for this purpose.
Glibc aleady uses a version number for its stat() calls, to permit
binary compatible extensions on the user side.
So all the mechanism is there AFAIK.
-- Jamie
next prev parent reply other threads:[~2002-10-28 15:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021027153651.GB26297@pimlott.net.suse.lists.linux.kernel>
[not found] ` <200210280947.g9S9l9H01162@sic.twinsun.com.suse.lists.linux.kernel>
2002-10-28 11:05 ` Andi Kleen
[not found] ` <20021028102809.GA16062@bjl1.asuk.net.suse.lists.linux.kernel>
2002-10-28 11:08 ` Andi Kleen
2002-10-28 12:56 ` Jamie Lokier
2002-10-28 14:15 ` Andi Kleen
2002-10-28 14:28 ` Maciej W. Rozycki
2002-10-28 15:13 ` Jamie Lokier [this message]
2002-10-28 15:40 ` Maciej W. Rozycki
2002-10-28 15:59 ` Jamie Lokier
2002-10-28 15:17 ` Jamie Lokier
[not found] <20021027153651.GB26297@pimlott.net>
2002-10-28 9:47 ` Paul Eggert
2002-10-28 10:28 ` Jamie Lokier
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=20021028151309.GB16546@bjl1.asuk.net \
--to=lk@tantalophile.demon.co.uk \
--cc=ak@suse.de \
--cc=eggert@twinsun.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
/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
all inboxes | Powered by JetHome®