tree acd84dfed3a2af3570982c6801ce674c9610cf9d
parent 3fed24fffc76dd1a8105db558e98bc8355d60379
author Matthew Wilcox (Oracle) <willy@infradead.org> 1708357273 +0000
committer Chandan Babu R <chandanbabu@kernel.org> 1708357773 +0530

xfs: Remove mrlock wrapper

mrlock was an rwsem wrapper that also recorded whether the lock was
held for read or write.  Now that we can ask the generic code whether
the lock is held for read or write, we can remove this wrapper and use
an rwsem directly.

As the comment says, we can't use lockdep to assert that the ILOCK is
held for write, because we might be in a workqueue, and we aren't able
to tell lockdep that we do in fact own the lock.

Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>