From: Jeffrey Altman <jaltman@auristor.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andreas Dilger <adilger@dilger.ca>,
David Howells <dhowells@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
linux-afs@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] afs: Add metadata xattrs
Date: Sat, 8 Jul 2017 22:37:53 -0400 [thread overview]
Message-ID: <01f6dcaa-b310-63fa-f43d-2acf44d734c3@auristor.com> (raw)
In-Reply-To: <20170709010155.3nql5ixdeozemgfd@thunk.org>
[-- Attachment #1.1: Type: text/plain, Size: 1301 bytes --]
On 7/8/2017 9:01 PM, Theodore Ts'o wrote:
> On Sat, Jul 08, 2017 at 12:44:54PM -0700, Linus Torvalds wrote:
>> Yeah, I think attributes are likely much better than some random crazy
>> ioctl interface. They can be listed with generic tools, and have
>> various scripting interfaces in ways that ioctl's do not sanely have.
>
> I personally don't have a particular problem with these xattrs. For
> one thing, they are read-only. You use them just to find out the AFS
> cell, the AFS "fid", and the AFS volume name.
>
> I think the place where people will start getting nervous is when we
> start adding "write-only" xattrs or where writing to an xattr causes a
> side-effect to take place.
Ted,
The list of AFS pioctls and the proposed alternatives for kAFS are
listed at
https://www.infradead.org/~dhowells/kafs/user_interface.html
While it is true that the majority of the proposed xattrs are read-only
properties of AFS objects (cell, volume, fid, servers, sec_class,
sec_mode) there is one exception that is read-write (acls). AuriStorFS
permits acls to be set per-file; there was some per-file acl work begun
for OpenAFS but it was never completed.
Is there an alternative for fetching and setting ACLs that should be
considered?
Jeffrey Altman
[-- Attachment #1.2: jaltman.vcf --]
[-- Type: text/x-vcard, Size: 410 bytes --]
begin:vcard
fn:Jeffrey Altman
n:Altman;Jeffrey
org:AuriStor, Inc.
adr:Suite 6B;;255 West 94Th Street;New York;New York;10025-6985;United States
email;internet:jaltman@auristor.com
title:Founder and CEO
tel;work:+1-212-769-9018
note;quoted-printable:LinkedIn: https://www.linkedin.com/in/jeffreyaltman=0D=0A=
Skype: jeffrey.e.altman=0D=0A=
url:https://www.auristor.com/
version:2.1
end:vcard
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4057 bytes --]
prev parent reply other threads:[~2017-07-09 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 14:50 [PATCH 0/2] AFS: Changes David Howells
2017-07-06 14:50 ` [PATCH 1/2] afs: Ignore AFS_ACE_READ and AFS_ACE_WRITE for directories David Howells
2017-07-06 14:50 ` [PATCH 2/2] afs: Add metadata xattrs David Howells
2017-07-06 15:23 ` Christoph Hellwig
2017-07-06 16:14 ` David Howells
2017-07-06 18:27 ` Andreas Dilger
2017-07-08 19:44 ` Linus Torvalds
2017-07-09 1:01 ` Theodore Ts'o
2017-07-09 2:37 ` Jeffrey Altman [this message]
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=01f6dcaa-b310-63fa-f43d-2acf44d734c3@auristor.com \
--to=jaltman@auristor.com \
--cc=adilger@dilger.ca \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®