public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: xiakaixu1987@gmail.com
Cc: linux-xfs@vger.kernel.org, david@fromorbit.com,
	hch@infradead.org, Kaixu Xia <kaixuxia@tencent.com>
Subject: Re: [RESEND PATCH 0/2] xfs: random fixes for lock flags
Date: Wed, 22 Jun 2022 16:28:32 -0700	[thread overview]
Message-ID: <YrOloCS1nZAPGq/E@magnolia> (raw)
In-Reply-To: <1655433034-17934-1-git-send-email-kaixuxia@tencent.com>

On Fri, Jun 17, 2022 at 10:30:32AM +0800, xiakaixu1987@gmail.com wrote:
> From: Kaixu Xia <kaixuxia@tencent.com>
> 
> Hi,
> 
> This patchset include some patches to factor out lock flags
> and fix the mmap_lock state check.

Funny that I didn't notice during review and nobody ever tripped
debugging assertions.

Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D


> Kaixu Xia (2):
>   xfs: factor out the common lock flags assert
>   xfs: use invalidate_lock to check the state of mmap_lock
> 
>  fs/xfs/xfs_inode.c | 64 ++++++++++++++++++----------------------------
>  1 file changed, 25 insertions(+), 39 deletions(-)
> 
> -- 
> 2.27.0
> 

      parent reply	other threads:[~2022-06-22 23:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  2:30 [RESEND PATCH 0/2] xfs: random fixes for lock flags xiakaixu1987
2022-06-17  2:30 ` [RESEND PATCH 1/2] xfs: factor out the common lock flags assert xiakaixu1987
2022-06-17 22:04   ` Dave Chinner
2022-06-17  2:30 ` [RESEND PATCH 2/2] xfs: use invalidate_lock to check the state of mmap_lock xiakaixu1987
2022-06-17 22:06   ` Dave Chinner
2022-06-22 23:28 ` Darrick J. Wong [this message]

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=YrOloCS1nZAPGq/E@magnolia \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=kaixuxia@tencent.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=xiakaixu1987@gmail.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