All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Yao <ryao@gentoo.org>
To: linux-nfs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: Making an interface for alternative data streams
Date: Mon, 21 Mar 2016 14:11:17 -0400	[thread overview]
Message-ID: <56F03945.40208@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 854 bytes --]

I am thinking of implementing Solaris-style alternative data streams in
the ZFSOnLinux driver via an ioctl and writing a compatibility shim so
that software written to use O_XATTR can be trivially adapted to use the
interface.

I sketched out the fine details on github:

https://github.com/zfsonlinux/zfs/issues/4437

I would be much happier if the VFS gave filesystem drivers the ability
to implement O_XATTR. That would avoid the need to (ab)use an ioctl for
this and eliminate the risk of using a bit that would be defined to mean
something else. The former risks permissions checks becoming stale while
the latter is a situation that I would be happy to avoid.

Since this sort of interface is applicable to NFS too, I wanted to ask
what various mainline developers think about it before I tried doing an
initial implementation.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

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

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 18:11 Richard Yao [this message]
2016-03-21 18:18 ` Making an interface for alternative data streams Christoph Hellwig
2016-03-21 18:51   ` Richard Yao
2016-03-21 19:17     ` Richard Yao
2016-03-21 20:19 ` Richard Yao
2016-03-21 20:40   ` J. Bruce Fields
2016-03-21 22:36     ` Theodore Ts'o
2016-03-21 22:48       ` Cedric Blancher
2016-03-22  0:12         ` J. Bruce Fields
2016-03-22  1:02           ` Richard Yao
2016-03-22  2:21             ` Richard Yao
2016-03-22 16:15               ` Richard Sharpe
2016-03-22 20:08                 ` J. Bruce Fields
2016-03-22 20:13                   ` Richard Sharpe
2016-03-22 20:32                     ` J. Bruce Fields
2016-03-22 21:42                   ` Jeremy Allison
2016-03-23  4:13                     ` Steve French
2016-03-23  4:19                       ` Steve French
2016-03-23 14:45                         ` Steve French
2016-03-23 17:01                           ` Jeremy Allison
2016-03-23 17:01                             ` Jeremy Allison
2016-03-23 17:16                             ` Steve French
2016-03-23 15:16                         ` J. Bruce Fields
2016-03-22  2:01     ` Richard Yao
2016-03-22 21:29       ` Dave Chinner
2016-03-22 21:52         ` J. Bruce Fields
2016-03-22 22:50           ` Dave Chinner

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=56F03945.40208@gentoo.org \
    --to=ryao@gentoo.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@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.