Skip to contentSkip to conversation

XATTRs in NFS?

DISCUSSION Matt W. Benjamin 5 participants 11 messages Oct 26, 2013 – Oct 28, 2013 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive

Hi,

Surely you don't need NFSv4 to standardize the the (empty?) set of system or magic attributes Linux should export?

Besides, as you're well aware, most people who ask for xattrs are looking for an ability to associate
arbitrary specific data, not a back door ioctl interface. That's clearly what the NFSv4 named attributes as standardized were intended for.

I'm well aware of other uses and plans that someone would want to standardize, but it seems irrelevant to the discussion.

Matt

Quoted 4 lines · ----- "Trond Myklebust

Standardise those xattrs, and we can export them specifically as part of the NFSv4 spec.

Signature · 10 lines
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 
#2 lore raw
Quoted 4 lines · Matt W. Benjamin

Hi,

Surely you don't need NFSv4 to standardize the the (empty?) set of system or magic attributes Linux should export?

The NFSv4 working group has no authority to do so. POSIX would be the right address.

Quoted 2 lines

Besides, as you're well aware, most people who ask for xattrs are looking for an ability to associate
arbitrary specific data, not a back door ioctl interface. That's clearly what the NFSv4 named attributes as standardized were intended for.

No. I'm not aware of that.

Quoted 2 lines

I'm well aware of other uses and plans that someone would want to standardize, but it seems irrelevant to the discussion.

It's very relevant to the discussion as it defines what namespace applications can expect to work.

Trond

#3 lore raw
Quoted 1 line · Trond

The NFSv4 working group has no authority to do so. POSIX would be the right address.

The complete lack of clue, authority or even defined semantics didn't stop them from defining their ACL model. User extended attributes are harmless compared to that, even if everyone has subtly different flavours.

#4 lore raw
Quoted 7 lines · Christoph Hellwig
Quoted 1 line · Trond

The NFSv4 working group has no authority to do so. POSIX would be the right address.

The complete lack of clue, authority or even defined semantics didn't stop them from defining their ACL model. User extended attributes are harmless compared to that, even if everyone has subtly different flavours.

+1

Signature · 1 line
Simo Sorce * Red Hat, Inc * New York
#5 lore raw
In reply to Christoph Hellwig
Quoted 8 lines · Christoph Hellwig
Quoted 1 line · Trond

The NFSv4 working group has no authority to do so. POSIX would be the right address.

The complete lack of clue, authority or even defined semantics didn't stop them from defining their ACL model. User extended attributes are harmless compared to that, even if everyone has subtly different flavours.

The user xattrs are in principle harmless. What about "trusted.*"?

BTW: caching any xattrs is a problem. There is no close-to-open model that you can use and neither is there locking. This is already causing a problem for labeled nfs...

Trond

#6 lore raw
Quoted 11 lines · Trond
Quoted 8 lines · Christoph Hellwig
Quoted 1 line · Trond

The NFSv4 working group has no authority to do so. POSIX would be the right address.

The complete lack of clue, authority or even defined semantics didn't stop them from defining their ACL model. User extended attributes are harmless compared to that, even if everyone has subtly different flavours.

Quoted 3 lines

The user xattrs are in principle harmless. What about "trusted.*"?

BTW: caching any xattrs is a problem. There is no close-to-open model that you can use and neither is there locking. This is already causing a problem for labeled nfs...

You could start without caching them.

Simo.

Signature · 1 line
Simo Sorce * Red Hat, Inc * New York
#7 lore raw
Quoted 12 lines · Simo Sorce
Quoted 11 lines · Trond
Quoted 8 lines · Christoph Hellwig
Quoted 1 line · Trond

The NFSv4 working group has no authority to do so. POSIX would be the right address.

The complete lack of clue, authority or even defined semantics didn't stop them from defining their ACL model. User extended attributes are harmless compared to that, even if everyone has subtly different flavours.

Quoted 6 lines
Quoted 3 lines

The user xattrs are in principle harmless. What about "trusted.*"?

BTW: caching any xattrs is a problem. There is no close-to-open model that you can use and neither is there locking. This is already causing a problem for labeled nfs...

You could start without caching them.

I'm not going to start anything...

Trond

#11 lore raw
In reply to Myklebust, Trond

Hi,

I was going for the point you make later in this thread: "user xattrs are in principle harmless."

The exposure policy for non-harmless xattrs issue is real enough, but my point was, it seems to be a Linux policy issue, at the NFSv4 level just as it was at the syscall level.

The caching and atomicity issues seem like they actually are issues for NFSv4 discussion. If the named attribute interface actually fails to cover xattrs, that's a big gaffe.

Matt

Quoted 28 lines · ----- "Trond Myklebust
Quoted 3 lines · Matt W. Benjamin

Hi,

Surely you don't need NFSv4 to standardize the the (empty?) set of

system or magic attributes Linux

Quoted 1 line

should export?

The NFSv4 working group has no authority to do so. POSIX would be the right address.

Quoted 1 line

Besides, as you're well aware, most people who ask for xattrs are

looking for an ability to associate

Quoted 1 line

arbitrary specific data, not a back door ioctl interface. That's

clearly what the NFSv4 named attributes as standardized were intended for.

No. I'm not aware of that.

Quoted 1 line

I'm well aware of other uses and plans that someone would want to

standardize, but it seems

Quoted 1 line

irrelevant to the discussion.

It's very relevant to the discussion as it defines what namespace applications can expect to work.

Trond

Signature · 10 lines
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 
#9 lore raw
Quoted 3 lines · Christoph Anton Mitterer
Quoted 1 line · Trond

I'm not going to start anything...

So that's basically a: "XATTRs in NFS - never"?! :(

Your case for adding the feature seems to be "I have a couple of programs that use xattrs, so NFS should provide it.".

Well, that means at a minimum going to the IETF (possibly also POSIX) to convince them that the feature is worth adding, helping design the protocol to do so, and achieving consensus in a NFSv4.x spec, then doing the work designing and coding up a Linux implementation. Who is volunteering to do all that?

My statement above was that I'm not volunteering to do all this. You haven't convinced me that your programs cannot be modified to use other more portable solutions. You're not even generating the checksums when creating the data, so there is already an existing window during which corruption can occur.

Trond

#10 lore raw
In reply to Myklebust, Trond
Quoted 1 line · Trond

The user xattrs are in principle harmless. What about "trusted.*"?

trusted ones are still fairly harmless and exist in most implementations under a slightly different name. They aren't quite as essential, though.

The important point is to not carry over the system and security namespacs. Those are a bad and Linux specific mistake to abuse the xattr interface for all kinds of other interfaces. This isn't something that should be carried over to other standards.