From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: Peter Chubb <peter@chubb.wattle.id.au>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org, ak@muc.de
Subject: Re: statfs64 missing
Date: Thu, 17 Oct 2002 23:27:16 +0200 [thread overview]
Message-ID: <4E53FFF4EC7@vcnet.vc.cvut.cz> (raw)
On 17 Oct 02 at 15:41, Benjamin LaHaise wrote:
> 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).
And if VFS could get access to dentry which was used for statfs,
I (and ncpfs) will be very happy, as then I can report space available
for user after applying directory restrictions just through normal
statfs call, instead of using own special call.
I understand that then it becomes more inode than superblock operation,
and that it is too late for 2.6...
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2002-10-17 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 21:27 Petr Vandrovec [this message]
-- 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-16 14:06 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
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=4E53FFF4EC7@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=ak@muc.de \
--cc=bcrl@redhat.com \
--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