[RFC] use a shared lock for VOP_GETEXTATTR

[Konstantin Belousov]

On Wed, Mar 27, 2013 at 06:37:51PM -0700, mdf at FreeBSD.org wrote:
> 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?

I think this change should be fine. At least it seems to for UFS.

What other filesystems did you audited ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 834 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20130328/173332e0/attachment.sig>