From: David Howells <dhowells@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: dhowells@redhat.com, Christoph Hellwig <hch@infradead.org>,
mtk.manpages@gmail.com,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: statx manpage
Date: Tue, 07 Mar 2017 18:39:42 +0000 [thread overview]
Message-ID: <10985.1488911982@warthog.procyon.org.uk> (raw)
In-Reply-To: <20170307180217.GF5281@birch.djwong.org>
Darrick J. Wong <darrick.wong@oracle.com> wrote:
> Is (flags & AT_EMPTY_PATH) is the same as (pathname == NULL)?
I'm not sure. I was wondering about that whilst writing this. The text
describing the option is copied from the stat(2) manpage. It specified an
empty path (presumably "") rather than NULL. I'm also not sure whether it has
other ramifications.
> > .I Note:
> > For performance and simplicity reasons, different fields in the
> > .I statx
> > structure may contain state information from different moments
> > during the execution of the system call.
>
> Hm. Judging from the ext4 patch you proposed, I gather this is
> expected, at least in the btime case.
This is copied from the stat(2) manpage. The comment in the source there says
it's because there's no locking in the getattr path against the setattr path.
David
next prev parent reply other threads:[~2017-03-07 18:50 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 0:06 [PATCH] xfs: report crtime and attribute flags to statx Darrick J. Wong
2017-03-07 5:01 ` Christoph Hellwig
2017-03-07 17:23 ` Darrick J. Wong
2017-03-07 17:22 ` statx manpage David Howells
2017-03-07 18:02 ` Darrick J. Wong
2017-03-07 18:39 ` David Howells [this message]
2017-03-07 18:44 ` Darrick J. Wong
2017-03-07 18:55 ` David Howells
2017-03-07 21:44 ` Andreas Dilger
2017-03-07 22:55 ` Eric Biggers
2017-03-08 3:45 ` Eryu Guan
2017-03-08 9:24 ` David Howells
2017-03-08 15:26 ` Jeff Layton
2017-03-20 16:01 ` Matthew Wilcox
2017-03-22 10:55 ` Jeff Layton
2017-03-08 9:41 ` David Howells
2017-03-10 5:01 ` Eric Biggers
2017-03-09 6:46 ` David Howells
2017-03-09 6:59 ` Eryu Guan
2017-03-09 6:59 ` Darrick J. Wong
2017-03-09 14:01 ` Christoph Hellwig
2017-03-09 7:45 ` David Howells
2017-03-24 20:53 ` Eric Biggers
2017-03-27 0:46 ` Andreas Dilger
2017-03-27 15:40 ` Darrick J. Wong
2017-03-27 16:25 ` David Howells
2017-03-27 16:46 ` Christoph Hellwig
2017-03-27 19:04 ` Jeff Layton
2017-03-28 19:39 ` Andreas Dilger
2017-03-28 20:22 ` Jeff Layton
2017-03-31 15:49 ` Christoph Hellwig
2017-03-27 18:57 ` David Howells
2017-03-28 0:13 ` [PATCH] Add initial batch of statx() LTP tests David Howells
2017-03-28 6:28 ` Christoph Hellwig
2017-03-28 8:23 ` David Howells
2017-03-27 9:55 ` statx manpage David Howells
2017-03-31 15:56 ` Christoph Hellwig
2017-03-31 16:43 ` David Howells
2017-03-31 16:43 ` David Howells
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=10985.1488911982@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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.