Clean up virtual xattrs

[gluster]

Clean up virtual xattrs

[jdarcy]

Even better, we should convert many (most?) virtual-xattr calls into the equivalent GF_FOP_IPC calls. Besides being cleaner, especially in the bidirectional-communication case, this completely avoids the problem of virtual xattrs mistakenly "leaking through" and being treated as real ones (as I recently had to address when "gf-internal-fop" was being passed to create).

[amarts]

👍 Lets start on this. For FS interface, we can just handle it in fuse layer with xattr() calls, but for both gfapi and everywhere else, this will be lot cleaner.

[amarts]

Planning to have provision for this FOP in new set of protocol XDRs. Will keep the request/response structure similar to xattr() calls itself. This will help not to break compatibility of protocol when this is completed.

[poornimag]

For virtual xattrs that act on the file that set/getxattr came on, will have a one additional costly step in IPC FOP, which is inode_find/resolve for the path/gfid, we need to optimise the same.

[stale]

Thank you for your contributions.
Noticed that this issue is not having any activity in last ~6 months! We are marking this issue as stale because it has not had recent activity.
It will be closed in 2 weeks if no one responds with a comment here.

[stale]

Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to open it.