From: Benjamin LaHaise <bcrl@redhat.com>
To: Andi Kleen <ak@muc.de>
Cc: Peter Chubb <peter@chubb.wattle.id.au>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: statfs64 missing
Date: Thu, 17 Oct 2002 15:41:02 -0400 [thread overview]
Message-ID: <20021017154102.D30332@redhat.com> (raw)
In-Reply-To: <20021017000111.GA25054@averell>; from ak@muc.de on Thu, Oct 17, 2002 at 02:01:11AM +0200
On Thu, Oct 17, 2002 at 02:01:11AM +0200, Andi Kleen wrote:
...
> So it boils down to if the new fields are important enough to justify
> the pain they cause on 64bit.
>
> (I ran into a similar issue with my nanosecond stat patchkit -
> alpha stat is 64bit clean, but doesn't have the padding for ns fields
> added used in later ports)
If any new stat() type syscalls are added, make sure that a length parameter
of the structure gets passed in from userland, as that way we will be able
to extend the available information without introducing yet another syscall
on every arch (this has happened enough times now that we should try to get
it right).
-ben
--
"Do you seek knowledge in time travel?"
next prev parent reply other threads:[~2002-10-17 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 14:06 statfs64 missing Andi Kleen
2002-10-16 14:16 ` Trond Myklebust
[not found] ` <15789.64263.606518.921166@wombat.chubb.wattle.id.au>
2002-10-17 0:01 ` Andi Kleen
2002-10-17 19:41 ` Benjamin LaHaise [this message]
2002-10-18 0:19 ` [PATCH] statfs64 no longer missing Peter Chubb
2002-10-18 0:26 ` Benjamin LaHaise
2002-10-18 2:31 ` Andi Kleen
2002-10-18 3:27 ` Peter Chubb
2002-10-18 6:17 ` Andreas Dilger
2002-10-18 6:31 ` Andi Kleen
2002-10-18 6:41 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-10-17 20:28 statfs64 missing Steven French
2002-10-17 21:55 ` Andreas Dilger
2002-10-17 21:27 Petr Vandrovec
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=20021017154102.D30332@redhat.com \
--to=bcrl@redhat.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--cc=trond.myklebust@fys.uio.no \
/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