From: Dave Chinner <david@fromorbit.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH 1/4] statx: Add a system call to make enhanced file info available
Date: Sat, 19 Nov 2016 08:27:25 +1100 [thread overview]
Message-ID: <20161118212725.GA31101@dastard> (raw)
In-Reply-To: <27040.1479464944@warthog.procyon.org.uk>
On Fri, Nov 18, 2016 at 10:29:04AM +0000, David Howells wrote:
> Dave Chinner <david@fromorbit.com> wrote:
>
> > > (13) FS_IOC_GETFLAGS value. These could be translated to BSD's st_flags.
> > > Note that the Linux IOC flags are a mess and filesystems such as Ext4
> > > define flags that aren't in linux/fs.h, so translation in the kernel
> > > may be a necessity (or, possibly, we provide the filesystem type too).
> >
> > And we now also have FS_IOC_FSGETXATTR that extends the flags
> > and information userspace can get from filesystems.
>
> Btw, can you point me at the manpage that defines the fsxattr struct and its
> flags?
man xfsctl is the original source. However, ....
> Also, ioctl_list(2) should probably include FS_IOC_FS[GS]ETXATTR.
... I thought patches had been sent to Michael to document them at
the VFS ioctl level. maybe I confused it with something else.....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-11-18 21:27 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 13:34 [RFC][PATCH 0/4] Enhanced file stat system call David Howells
2016-11-17 13:35 ` [PATCH 1/4] statx: Add a system call to make enhanced file info available David Howells
2016-11-17 18:39 ` Jeff Layton
2016-11-18 2:32 ` Andreas Dilger
2016-11-18 8:59 ` David Howells
2016-11-18 9:25 ` Andreas Dilger
2016-11-17 23:40 ` Dave Chinner
2016-11-18 3:28 ` Andreas Dilger
2016-11-18 22:07 ` Dave Chinner
2016-11-18 22:54 ` David Howells
2016-11-19 22:43 ` Dave Chinner
2016-11-21 14:30 ` One Thousand Gnomes
2016-11-21 20:43 ` Dave Chinner
2016-11-22 10:39 ` David Howells
2016-11-22 13:55 ` Jeff Layton
2016-11-22 20:58 ` Dave Chinner
2016-11-18 9:53 ` David Howells
2016-11-18 8:48 ` David Howells
2016-11-18 12:01 ` Jeff Layton
2016-11-18 9:36 ` David Howells
2016-11-18 17:17 ` Jeff Layton
2016-11-18 18:04 ` David Howells
2016-11-18 18:54 ` Jeff Layton
2016-11-18 19:08 ` David Howells
2016-11-18 9:43 ` David Howells
2016-11-18 21:41 ` Dave Chinner
2016-11-18 22:24 ` David Howells
2016-11-18 10:29 ` David Howells
2016-11-18 21:27 ` Dave Chinner [this message]
2016-11-18 21:48 ` David Howells
2016-11-18 22:17 ` Dave Chinner
2016-11-19 10:21 ` Michael Kerrisk (man-pages)
2016-11-17 13:35 ` [PATCH 2/4] statx: Ext4: Return enhanced file attributes David Howells
2016-11-18 3:30 ` Andreas Dilger
2016-11-17 13:35 ` [PATCH 3/4] statx: NFS: " David Howells
2016-11-17 13:35 ` [PATCH 4/4] statx: AFS: " David Howells
2016-11-18 3:34 ` Andreas Dilger
2016-11-18 8:47 ` David Howells
2016-11-17 14:39 ` [RFC][PATCH 0/4] Enhanced file stat system call One Thousand Gnomes
2016-11-17 15:10 ` Michael Kerrisk
2016-11-17 16:33 ` David Howells
2016-11-17 16:45 ` David Howells
2016-11-17 20:00 ` J. Bruce Fields
2016-11-18 2:30 ` Andreas Dilger
2016-11-18 4:29 ` NeilBrown
2016-11-18 13:41 ` One Thousand Gnomes
2016-11-18 13:49 ` 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=20161118212725.GA31101@dastard \
--to=david@fromorbit.com \
--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).