From: Jeff Garzik <jeff@garzik.org>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: linux-fsdevel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] VFS "stat light" out of fstatat, and fine grained flags
Date: Tue, 07 Apr 2009 19:25:45 -0400 [thread overview]
Message-ID: <49DBE0F9.7000207@garzik.org> (raw)
In-Reply-To: <20090407231524.GA1569655@fiona.linuxhacker.ru>
Oleg Drokin wrote:
> Hello!
>
> This is reworked Mark Fasheh's patch + my earlier patch.
> It allows one to specify which specific struct stat fields are needed
> out of the fstatat call, and also a request to obtain most uptodate
> information for inode (for NFS mostly).
>
> Also it adds AT_STAT_SELF flag to mean that the stat should be executed not
> on a path, but on the passed filedecriptor itself.
>
> A first real kernel user for this added in loop block driver that does
> not care about size or anything else besides rdev and inode number.
>
> I see various architectures replicate bits of vfs_*stat* in some compat
> code, I am not sure if we need to update those as well or not.
>
> This patch does away with all the extra syscalls.
linux-kernel should be included in the discussion of this syscall.
Jeff
next prev parent reply other threads:[~2009-04-07 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 23:15 [PATCH 1/3] VFS "stat light" out of fstatat, and fine grained flags Oleg Drokin
2009-04-07 23:25 ` Jeff Garzik [this message]
2009-04-08 6:56 ` forwarding -fsdevel to -kernel (was Re: [PATCH 1/3] VFS "stat ...) flags Miklos Szeredi
2009-04-08 7:35 ` David Miller
2009-04-12 20:50 ` [PATCH 1/3] VFS "stat light" out of fstatat, and fine grained flags Jamie Lokier
2009-04-12 21:46 ` Oleg Drokin
2009-04-21 10:20 ` VFS "stat light" fstatat, inconsistent *at() function interfaces 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=49DBE0F9.7000207@garzik.org \
--to=jeff@garzik.org \
--cc=green@linuxhacker.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).