linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Reichl <preichl@redhat.com>
To: linux-xfs@vger.kernel.org
Cc: Pavel Reichl <preichl@redhat.com>
Subject: [PATCH v2 0/7] xfs: Remove wrappers for some semaphores
Date: Mon,  3 Feb 2020 18:58:43 +0100	[thread overview]
Message-ID: <20200203175850.171689-1-preichl@redhat.com> (raw)

Remove some wrappers that we have in XFS around the read-write semaphore
locks.

The goal of cleanup is to remove mrlock_t structure and its mr*()
wrapper functions and replace it with native rw_semaphore type and its
native calls.

Pavel Reichl (7):
  xfs: Add xfs_is_{i,io,mmap}locked functions
  xfs: Update checking excl. locks for ilock
  xfs: Update checking read or write locks for ilock
  xfs: Update checking for iolock
  xfs: Update checking for mmaplock
  xfs: update excl. lock check for IOLOCK and ILOCK
  xfs: Replace mrlock_t by rw_semaphore

 fs/xfs/libxfs/xfs_attr.c        |   2 +-
 fs/xfs/libxfs/xfs_attr_remote.c |   2 +-
 fs/xfs/libxfs/xfs_bmap.c        |  22 +++---
 fs/xfs/libxfs/xfs_inode_fork.c  |   2 +-
 fs/xfs/libxfs/xfs_rtbitmap.c    |   2 +-
 fs/xfs/libxfs/xfs_trans_inode.c |   6 +-
 fs/xfs/mrlock.h                 |  78 ----------------------
 fs/xfs/xfs_attr_list.c          |   2 +-
 fs/xfs/xfs_bmap_util.c          |   8 +--
 fs/xfs/xfs_dquot.c              |   4 +-
 fs/xfs/xfs_file.c               |   5 +-
 fs/xfs/xfs_inode.c              | 114 ++++++++++++++++++++------------
 fs/xfs/xfs_inode.h              |  10 ++-
 fs/xfs/xfs_inode_item.c         |   4 +-
 fs/xfs/xfs_iops.c               |  12 ++--
 fs/xfs/xfs_linux.h              |   1 -
 fs/xfs/xfs_qm.c                 |  12 ++--
 fs/xfs/xfs_reflink.c            |   2 +-
 fs/xfs/xfs_rtalloc.c            |   4 +-
 fs/xfs/xfs_super.c              |   6 +-
 fs/xfs/xfs_symlink.c            |   2 +-
 fs/xfs/xfs_trans_dquot.c        |   2 +-
 22 files changed, 127 insertions(+), 175 deletions(-)
 delete mode 100644 fs/xfs/mrlock.h

-- 
2.24.1


             reply	other threads:[~2020-02-03 17:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 17:58 Pavel Reichl [this message]
2020-02-03 17:58 ` [PATCH v2 1/7] xfs: Add xfs_is_{i,io,mmap}locked functions Pavel Reichl
2020-02-03 21:00   ` Chaitanya Kulkarni
2020-02-03 23:15   ` Dave Chinner
2020-02-03 23:45   ` Eric Sandeen
2020-02-04  6:19   ` Christoph Hellwig
2020-02-03 17:58 ` [PATCH v2 2/7] xfs: Update checking excl. locks for ilock Pavel Reichl
2020-02-03 23:16   ` Dave Chinner
2020-02-04  6:21   ` Christoph Hellwig
2020-02-04 16:08     ` Eric Sandeen
2020-02-04 21:06       ` Dave Chinner
2020-02-04 22:20         ` Eric Sandeen
2020-02-03 17:58 ` [PATCH v2 3/7] xfs: Update checking read or write " Pavel Reichl
2020-02-03 23:18   ` Dave Chinner
2020-02-03 17:58 ` [PATCH v2 4/7] xfs: Update checking for iolock Pavel Reichl
2020-02-03 23:24   ` Dave Chinner
2020-02-03 17:58 ` [PATCH v2 5/7] xfs: Update checking for mmaplock Pavel Reichl
2020-02-03 23:25   ` Dave Chinner
2020-02-03 17:58 ` [PATCH v2 6/7] xfs: update excl. lock check for IOLOCK and ILOCK Pavel Reichl
2020-02-03 23:35   ` Dave Chinner
2020-02-03 17:58 ` [PATCH v2 7/7] xfs: Replace mrlock_t by rw_semaphore Pavel Reichl

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=20200203175850.171689-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).