From: Brian Foster <bfoster@redhat.com>
To: Pavel Reichl <preichl@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v11 1/4] xfs: Refactor xfs_isilocked()
Date: Thu, 15 Oct 2020 06:32:39 -0400 [thread overview]
Message-ID: <20201015103239.GA1123529@bfoster> (raw)
In-Reply-To: <fbbead0a-c691-f870-a33d-b80a6177ce4f@redhat.com>
On Wed, Oct 14, 2020 at 11:04:31PM +0200, Pavel Reichl wrote:
>
>
> On 10/12/20 6:03 PM, Brian Foster wrote:
> > On Fri, Oct 09, 2020 at 09:55:12PM +0200, Pavel Reichl wrote:
> >> Refactor xfs_isilocked() to use newly introduced __xfs_rwsem_islocked().
> >> __xfs_rwsem_islocked() is a helper function which encapsulates checking
> >> state of rw_semaphores hold by inode.
> >>
> >> Signed-off-by: Pavel Reichl <preichl@redhat.com>
> >> Suggested-by: Dave Chinner <dchinner@redhat.com>
> >> Suggested-by: Eric Sandeen <sandeen@redhat.com>
> >> Suggested-by: Darrick J. Wong <darrick.wong@oracle.com>
> >> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
> >> ---
> >> fs/xfs/xfs_inode.c | 48 ++++++++++++++++++++++++++++++++++++++--------
> >> fs/xfs/xfs_inode.h | 21 +++++++++++++-------
> >> 2 files changed, 54 insertions(+), 15 deletions(-)
> >>
> >> diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> >> index c06129cffba9..7c1ceb4df4ec 100644
> >> --- a/fs/xfs/xfs_inode.c
> >> +++ b/fs/xfs/xfs_inode.c
> >> @@ -345,9 +345,43 @@ xfs_ilock_demote(
> >> }
> >>
> >> #if defined(DEBUG) || defined(XFS_WARN)
> >> -int
> >> +static inline bool
> >> +__xfs_rwsem_islocked(
> >> + struct rw_semaphore *rwsem,
> >> + int lock_flags)
> >> +{
> >> + int arg;
> >> +
> >> + if (!debug_locks)
> >> + return rwsem_is_locked(rwsem);
> >> +
> >> + if (lock_flags & (1 << XFS_SHARED_LOCK_SHIFT)) {
> >> + /*
> >> + * The caller could be asking if we have (shared | excl)
> >> + * access to the lock. Ask lockdep if the rwsem is
> >> + * locked either for read or write access.
> >> + *
> >> + * The caller could also be asking if we have only
> >> + * shared access to the lock. Holding a rwsem
> >> + * write-locked implies read access as well, so the
> >> + * request to lockdep is the same for this case.
> >> + */
> >> + arg = -1;
> >> + } else {
> >> + /*
> >> + * The caller is asking if we have only exclusive access
> >> + * to the lock. Ask lockdep if the rwsem is locked for
> >> + * write access.
> >> + */
> >> + arg = 0;
> >> + }
> ...
> >
> > Also, I find the pattern of shifting in the caller slightly confusing,
> > particularly with the 'lock_flags' name being passed down through the
> > caller. Any reason we couldn't pass the shift value as a parameter and
> > do the shift at the top of the function so the logic is clear and in one
> > place?
> >
>
> Hi Brian, is following change what you had in mind? Thanks!
>
Yep, pretty much. I find shifted_lock_flags to be a little verbose as a
name. I'd be fine with just doing something like 'lock_flags >>= shift'
near the top of the function, but that's more of a personal nit. I also
like Christoph's suggestion to avoid the arg variable (along with the
comment update suggested in the discussion with Darrick).
Brian
>
> >> @@ -349,14 +349,16 @@ xfs_ilock_demote(
> static inline bool
> __xfs_rwsem_islocked(
> struct rw_semaphore *rwsem,
> - int lock_flags)
> + int lock_flags,
> + int shift)
> {
> int arg;
> + const int shifted_lock_flags = lock_flags >> shift;
>
> if (!debug_locks)
> return rwsem_is_locked(rwsem);
>
> - if (lock_flags & (1 << XFS_SHARED_LOCK_SHIFT)) {
> + if (shifted_lock_flags & (1 << XFS_SHARED_LOCK_SHIFT)) {
> /*
> * The caller could be asking if we have (shared | excl)
> * access to the lock. Ask lockdep if the rwsem is
> @@ -387,20 +389,20 @@ xfs_isilocked(
> {
> if (lock_flags & (XFS_ILOCK_EXCL | XFS_ILOCK_SHARED)) {
> ASSERT(!(lock_flags & ~(XFS_ILOCK_EXCL | XFS_ILOCK_SHARED)));
> - return __xfs_rwsem_islocked(&ip->i_lock,
> - (lock_flags >> XFS_ILOCK_FLAG_SHIFT));
> + return __xfs_rwsem_islocked(&ip->i_lock, lock_flags,
> + XFS_ILOCK_FLAG_SHIFT);
> }
>
> if (lock_flags & (XFS_MMAPLOCK_EXCL | XFS_MMAPLOCK_SHARED)) {
> ASSERT(!(lock_flags &
> ~(XFS_MMAPLOCK_EXCL | XFS_MMAPLOCK_SHARED)));
> - return __xfs_rwsem_islocked(&ip->i_mmaplock,
> - (lock_flags >> XFS_MMAPLOCK_FLAG_SHIFT));
> + return __xfs_rwsem_islocked(&ip->i_mmaplock, lock_flags,
> + XFS_MMAPLOCK_FLAG_SHIFT);
> }
>
> if (lock_flags & (XFS_IOLOCK_EXCL | XFS_IOLOCK_SHARED)) {
> - return __xfs_rwsem_islocked(&VFS_I(ip)->i_rwsem,
> - (lock_flags >> XFS_IOLOCK_FLAG_SHIFT));
> + return __xfs_rwsem_islocked(&VFS_I(ip)->i_rwsem, lock_flags,
> + XFS_IOLOCK_FLAG_SHIFT);
> }
>
> ASSERT(0);
>
next prev parent reply other threads:[~2020-10-15 10:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 19:55 [PATCH v11 0/4] xfs: Remove wrappers for some semaphores Pavel Reichl
2020-10-09 19:55 ` [PATCH v11 1/4] xfs: Refactor xfs_isilocked() Pavel Reichl
2020-10-12 16:03 ` Brian Foster
2020-10-12 21:28 ` Darrick J. Wong
2020-10-13 11:04 ` Brian Foster
2020-10-14 21:04 ` Pavel Reichl
2020-10-15 10:32 ` Brian Foster [this message]
2020-10-15 8:20 ` Christoph Hellwig
2020-10-09 19:55 ` [PATCH v11 2/4] xfs: clean up whitespace in xfs_isilocked() calls Pavel Reichl
2020-10-12 16:03 ` Brian Foster
2020-10-15 8:17 ` Christoph Hellwig
2020-10-09 19:55 ` [PATCH v11 3/4] xfs: xfs_isilocked() can only check a single lock type Pavel Reichl
2020-10-12 16:03 ` Brian Foster
2020-10-15 8:17 ` Christoph Hellwig
2020-10-09 19:55 ` [PATCH v11 4/4] xfs: replace mrlock_t with rw_semaphores Pavel Reichl
2020-10-12 16:04 ` Brian Foster
2020-10-12 20:44 ` Pavel Reichl
2020-10-13 11:04 ` Brian Foster
2020-10-13 13:39 ` Pavel Reichl
2020-10-13 13:49 ` Brian Foster
2020-10-12 21:02 ` Pavel Reichl
2020-10-12 21:30 ` Darrick J. Wong
2020-10-13 11:07 ` Brian Foster
2020-10-15 8:21 ` Christoph Hellwig
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=20201015103239.GA1123529@bfoster \
--to=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=preichl@redhat.com \
/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).