From: "Darrick J. Wong" <djwong@kernel.org>
To: Zhang Yi <yi.zhang@huaweicloud.com>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, hch@infradead.org,
brauner@kernel.org, david@fromorbit.com, tytso@mit.edu,
jack@suse.cz, yi.zhang@huawei.com, chengzhihao1@huawei.com,
yukuai3@huawei.com
Subject: Re: [PATCH 1/4] xfs: match lock mode in xfs_buffered_write_iomap_begin()
Date: Mon, 11 Mar 2024 08:34:15 -0700 [thread overview]
Message-ID: <20240311153415.GS1927156@frogsfrogsfrogs> (raw)
In-Reply-To: <20240311122255.2637311-2-yi.zhang@huaweicloud.com>
On Mon, Mar 11, 2024 at 08:22:52PM +0800, Zhang Yi wrote:
> From: Zhang Yi <yi.zhang@huawei.com>
>
> Commit 1aa91d9c9933 ("xfs: Add async buffered write support") replace
> xfs_ilock(XFS_ILOCK_EXCL) with xfs_ilock_for_iomap() when locking the
> writing inode, and a new variable lockmode is used to indicate the lock
> mode. Although the lockmode should always be XFS_ILOCK_EXCL, it's still
> better to use this variable instead of useing XFS_ILOCK_EXCL directly
> when unlocking the inode.
>
> Fixes: 1aa91d9c9933 ("xfs: Add async buffered write support")
AFAICT, xfs_ilock_for_iomap can change lockmode from SHARED->EXCL, but
never changed away from EXCL, right? And xfs_buffered_write_iomap_begin
sets it to EXCL (and never changes it), right?
This seems like more of a code cleanup/logic bomb removal than an actual
defect that someone could actually hit, correct?
If the answers are {yes, yes, yes} then:
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
> ---
> fs/xfs/xfs_iomap.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c
> index 18c8f168b153..ccf83e72d8ca 100644
> --- a/fs/xfs/xfs_iomap.c
> +++ b/fs/xfs/xfs_iomap.c
> @@ -1149,13 +1149,13 @@ xfs_buffered_write_iomap_begin(
> * them out if the write happens to fail.
> */
> seq = xfs_iomap_inode_sequence(ip, IOMAP_F_NEW);
> - xfs_iunlock(ip, XFS_ILOCK_EXCL);
> + xfs_iunlock(ip, lockmode);
> trace_xfs_iomap_alloc(ip, offset, count, allocfork, &imap);
> return xfs_bmbt_to_iomap(ip, iomap, &imap, flags, IOMAP_F_NEW, seq);
>
> found_imap:
> seq = xfs_iomap_inode_sequence(ip, 0);
> - xfs_iunlock(ip, XFS_ILOCK_EXCL);
> + xfs_iunlock(ip, lockmode);
> return xfs_bmbt_to_iomap(ip, iomap, &imap, flags, 0, seq);
>
> found_cow:
> @@ -1165,17 +1165,17 @@ xfs_buffered_write_iomap_begin(
> if (error)
> goto out_unlock;
> seq = xfs_iomap_inode_sequence(ip, IOMAP_F_SHARED);
> - xfs_iunlock(ip, XFS_ILOCK_EXCL);
> + xfs_iunlock(ip, lockmode);
> return xfs_bmbt_to_iomap(ip, iomap, &cmap, flags,
> IOMAP_F_SHARED, seq);
> }
>
> xfs_trim_extent(&cmap, offset_fsb, imap.br_startoff - offset_fsb);
> - xfs_iunlock(ip, XFS_ILOCK_EXCL);
> + xfs_iunlock(ip, lockmode);
> return xfs_bmbt_to_iomap(ip, iomap, &cmap, flags, 0, seq);
>
> out_unlock:
> - xfs_iunlock(ip, XFS_ILOCK_EXCL);
> + xfs_iunlock(ip, lockmode);
> return error;
> }
>
> --
> 2.39.2
>
>
next prev parent reply other threads:[~2024-03-11 15:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 12:22 [PATCH 0/4] xfs/iomap: fix non-atomic clone operation and don't update size when zeroing range post eof Zhang Yi
2024-03-11 12:22 ` [PATCH 1/4] xfs: match lock mode in xfs_buffered_write_iomap_begin() Zhang Yi
2024-03-11 15:34 ` Darrick J. Wong [this message]
2024-03-12 8:18 ` Zhang Yi
2024-03-12 12:16 ` Christoph Hellwig
2024-03-11 12:22 ` [PATCH 2/4] xfs: convert delayed extents to unwritten when zeroing post eof blocks Zhang Yi
2024-03-11 15:37 ` Darrick J. Wong
2024-03-12 12:21 ` Christoph Hellwig
2024-03-12 12:44 ` Zhang Yi
2024-03-12 12:31 ` Zhang Yi
2024-03-12 16:21 ` Darrick J. Wong
2024-03-13 7:07 ` Zhang Yi
2024-03-13 13:25 ` Zhang Yi
2024-03-13 20:05 ` Darrick J. Wong
2024-03-11 12:22 ` [PATCH 3/4] iomap: don't increase i_size if it's not a write operation Zhang Yi
2024-03-11 15:48 ` Darrick J. Wong
2024-03-12 12:22 ` Christoph Hellwig
2024-03-12 12:59 ` Zhang Yi
2024-03-12 16:24 ` Darrick J. Wong
2024-03-13 7:09 ` Zhang Yi
2024-03-11 12:22 ` [PATCH 4/4] iomap: cleanup iomap_write_iter() Zhang Yi
2024-03-11 16:07 ` Darrick J. Wong
2024-03-12 12:24 ` Christoph Hellwig
2024-03-12 16:27 ` Darrick J. Wong
2024-03-13 9:23 ` Zhang Yi
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=20240311153415.GS1927156@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=chengzhihao1@huawei.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.com \
--cc=yi.zhang@huaweicloud.com \
--cc=yukuai3@huawei.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