From: Jeff Garzik <jeff@garzik.org>
To: Andreas Dilger <adilger@sun.com>
Cc: Oleg Drokin <green@linuxhacker.ru>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: Attempt at "stat light" implementation
Date: Tue, 07 Apr 2009 15:48:40 -0400 [thread overview]
Message-ID: <49DBAE18.20406@garzik.org> (raw)
In-Reply-To: <20090407182809.GX3204@webber.adilger.int>
Andreas Dilger wrote:
> On Apr 07, 2009 13:56 -0400, Oleg Drokin wrote:
>> On Apr 7, 2009, at 1:49 PM, Christoph Hellwig wrote:
>>> I think the best way to do it is to just define additional flags for
>>> *statat family, that if present only request partial stat information.
>> But having to open every dir (or take an extra intermediate lookup hit)
>> might be a bad thing at times unless we officially allow to use a
>> "magic" > "AT_FDCWD". What's your opinion on this?
>
> Generally, any application doing tree traversal will have the parent
> directory open doing readdir() or getdents() so I don't think that is
> a huge problem.
And if that application does not have a directory open, it is vulnerable
to races...
Jeff
next prev parent reply other threads:[~2009-04-07 19:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 6:23 Attempt at "stat light" implementation Oleg Drokin
2009-04-07 10:23 ` Andreas Dilger
2009-04-07 14:54 ` Oleg Drokin
2009-04-07 17:52 ` Christoph Hellwig
2009-04-07 15:22 ` jim owens
2009-04-07 15:38 ` Oleg Drokin
2009-04-07 16:20 ` jim owens
2009-04-07 17:32 ` Jamie Lokier
2009-04-07 17:38 ` Jeff Garzik
2009-04-07 17:56 ` Jamie Lokier
2009-04-07 18:21 ` Andreas Dilger
2009-04-07 19:30 ` Ulrich Drepper
2009-04-12 20:55 ` Jamie Lokier
2009-04-07 17:41 ` Oleg Drokin
2009-04-07 17:54 ` Jamie Lokier
2009-04-07 18:00 ` Oleg Drokin
2009-04-07 18:18 ` Andreas Dilger
2009-04-07 18:31 ` Nicholas Miell
2009-04-07 17:49 ` Christoph Hellwig
2009-04-07 17:56 ` Oleg Drokin
2009-04-07 18:28 ` Andreas Dilger
2009-04-07 18:50 ` Jamie Lokier
2009-04-07 19:48 ` Jeff Garzik [this message]
2009-04-07 19:47 ` Jeff Garzik
2009-04-07 20:18 ` Evgeniy Polyakov
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=49DBAE18.20406@garzik.org \
--to=jeff@garzik.org \
--cc=adilger@sun.com \
--cc=green@linuxhacker.ru \
--cc=hch@infradead.org \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.