[RFC] use a shared lock for VOP_GETEXTATTR

[mdf at FreeBSD.org]

VOP_GETEXTATTR is currently called with an exclusive lock, which seems
like overkill for what is essentially a read operation.  I had a look
over the various in-tree filesystems and it didn't look like any of
them will have a problem if a shared-mode lock is used for
vop_getextattr.

Does anyone know otherwise?  Is someone using extended attributes
regularly who can test this?

[sorry if this is a duplicate; I first sent from my non-FreeBSD mail]

Thanks,
matthew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Use-a-shared-lock-for-VOP_GETEXTATTR-as-it-is-a-read.patch
Type: application/octet-stream
Size: 1801 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20130327/d998a183/attachment.obj>