From: Arnd Bergmann <arnd@arndb.de>
To: David Howells <dhowells@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] statx: Add a system call to make enhanced file info available [ver #2]
Date: Fri, 18 Nov 2016 17:57:55 +0100 [thread overview]
Message-ID: <2756474.23HNgnMOUG@wuerfel> (raw)
In-Reply-To: <147948603812.5122.5116851833739815967.stgit@warthog.procyon.org.uk>
On Friday, November 18, 2016 4:20:38 PM CET David Howells wrote:
> Add a system call to make extended file information available, including
> file creation and some attribute flags where available through the
> underlying filesystem.
Looks great!
Is there still hope of scheduling this for v4.10, or are you
planning it for v4.11 at this point?
> ========
> OVERVIEW
> ========
>
> The idea was initially proposed as a set of xattrs that could be retrieved
> with getxattr(), but the general preferance proved to be for a new syscall
> with an extended stat structure.
>
> This has a number of uses:
...
>
> Note that not all of the above are implemented here.
It's good to have the whole list of possible features here, but
the list of features that are actually implemented is probably
more important for the changelog. You seem to have that list
in the introductory mail but not in the actual patch.
> - stat->atime = inode->i_atime;
>
> stat->mtime = inode->i_mtime;
> stat->ctime = inode->i_ctime;
>
> - stat->blksize = (1 << inode->i_blkbits);
> + stat->size = i_size_read(inode);
>
> stat->blocks = inode->i_blocks;
>
> -}
> + stat->blksize = 1 << inode->i_blkbits;
>
> + stat->result_mask |= STATX_BASIC_STATS;
> + if (IS_NOATIME(inode))
> + stat->result_mask &= ~STATX_ATIME;
> + else
> + stat->atime = inode->i_atime;
This looks like you are changing the behavior of the existing
stat call to no longer return the atime from the on-disk
inode if NOATIME is set.
Is my interpretation correct, and is this an intentional
change?
Arnd
next prev parent reply other threads:[~2016-11-18 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 16:20 [RFC][PATCH 0/4] Enhanced file stat system call [ver #2] David Howells
2016-11-18 16:20 ` [PATCH 1/4] statx: Add a system call to make enhanced file info available " David Howells
2016-11-18 16:57 ` Arnd Bergmann [this message]
2016-11-18 16:20 ` [PATCH 2/4] statx: Ext4: Return enhanced file attributes " David Howells
2016-11-18 18:02 ` Andreas Dilger
[not found] ` <147948603103.5122.1043337990092830185.stgit-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2016-11-18 16:20 ` [PATCH 3/4] statx: NFS: " David Howells
2016-11-18 16:20 ` [PATCH 4/4] statx: AFS: " 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=2756474.23HNgnMOUG@wuerfel \
--to=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=linux-api@vger.kernel.org \
--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).