linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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

  reply	other threads:[~2016-11-18 21:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2D8B8AAF-2016-45BD-9D70-A532DDDB23D2@dilger.ca>
     [not found] ` <147938969703.13574.10295364502230379833.stgit@warthog.procyon.org.uk>
2016-11-17 15:10   ` [RFC][PATCH 0/4] Enhanced file stat system call Michael Kerrisk
2016-11-17 16:33   ` David Howells
     [not found]   ` <147938970382.13574.11581172952175034619.stgit@warthog.procyon.org.uk>
     [not found]     ` <1479407964.4556.5.camel@redhat.com>
     [not found]       ` <2D8B8AAF-2016-45BD-9D70-A532DDDB23D2-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org>
2016-11-18  8:59         ` [PATCH 1/4] statx: Add a system call to make enhanced file info available David Howells
     [not found]           ` <25517.1479459564-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2016-11-18  9:25             ` Andreas Dilger
2016-11-18 10:29     ` David Howells
2016-11-18 21:27       ` Dave Chinner [this message]
2016-11-18 21:48       ` David Howells
     [not found]         ` <9903.1479505701-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2016-11-18 22:17           ` Dave Chinner
2016-11-19 10:21             ` Michael Kerrisk (man-pages)

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).