On Wed, Mar 27, 2013 at 10:40:16PM -0700, m...@freebsd.org wrote:
> On Wed, Mar 27, 2013 at 10:32 PM, Konstantin Belousov
> wrote:
> > On Wed, Mar 27, 2013 at 06:37:51PM -0700, m...@freebsd.org wrote:
> >> VOP_GETEXTATTR is currently called with an exclusive lock, which seems
> >> like overkill fo
On Wed, Mar 27, 2013 at 10:32 PM, Konstantin Belousov
wrote:
> On Wed, Mar 27, 2013 at 06:37:51PM -0700, m...@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
On Wed, Mar 27, 2013 at 06:37:51PM -0700, m...@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
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 kn
