From: Pavel Reichl <preichl@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH v8 0/4] xfs: Remove wrappers for some semaphores
Date: Mon, 5 Oct 2020 23:38:48 +0200 [thread overview]
Message-ID: <20201005213852.233004-1-preichl@redhat.com> (raw)
Remove some wrappers that we have in XFS around the read-write semaphore
locks.
The goal of this cleanup is to remove mrlock_t structure and its mr*()
wrapper functions and replace it with native rw_semaphore type and its
native calls.
Changes in version 8:
Patchset was rebased so it applies cleanly.
The patch 'xfs: replace mrlock_t with rw_semaphores' contains change in
xfs_btree.c which transfers ownership of lock so lockdep won't assert
(This was reported by Darrick and proposed change fixes this issue).
Pavel Reichl (4):
xfs: Refactor xfs_isilocked()
xfs: clean up whitespace in xfs_isilocked() calls
xfs: xfs_isilocked() can only check a single lock type
xfs: replace mrlock_t with rw_semaphores
fs/xfs/libxfs/xfs_bmap.c | 8 +--
fs/xfs/libxfs/xfs_btree.c | 10 ++++
fs/xfs/mrlock.h | 78 -----------------------------
fs/xfs/xfs_file.c | 3 +-
fs/xfs/xfs_inode.c | 102 +++++++++++++++++++++++++-------------
fs/xfs/xfs_inode.h | 25 ++++++----
fs/xfs/xfs_iops.c | 4 +-
fs/xfs/xfs_linux.h | 2 +-
fs/xfs/xfs_qm.c | 2 +-
fs/xfs/xfs_super.c | 6 +--
10 files changed, 107 insertions(+), 133 deletions(-)
delete mode 100644 fs/xfs/mrlock.h
--
2.26.2
next reply other threads:[~2020-10-05 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 21:38 Pavel Reichl [this message]
2020-10-05 21:38 ` [PATCH v8 1/4] xfs: Refactor xfs_isilocked() Pavel Reichl
2020-10-06 4:16 ` Darrick J. Wong
2020-10-05 21:38 ` [PATCH v8 2/4] xfs: clean up whitespace in xfs_isilocked() calls Pavel Reichl
2020-10-06 4:16 ` Darrick J. Wong
2020-10-05 21:38 ` [PATCH v8 3/4] xfs: xfs_isilocked() can only check a single lock type Pavel Reichl
2020-10-06 4:16 ` Darrick J. Wong
2020-10-05 21:38 ` [PATCH v8 4/4] xfs: replace mrlock_t with rw_semaphores Pavel Reichl
2020-10-06 4:14 ` Darrick J. Wong
2020-10-06 10:50 ` Pavel Reichl
2020-10-06 13:54 ` Eric Sandeen
2020-10-06 14:04 ` Eric Sandeen
2020-10-06 15:28 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201005213852.233004-1-preichl@redhat.com \
--to=preichl@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.