From: "Darrick J. Wong" <djwong@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: chandanbabu@kernel.org, cem@kernel.org, brauner@kernel.org,
dchinner@redhat.com, yi.zhang@huawei.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: Propagate errors from xfs_reflink_cancel_cow_range in xfs_dax_write_iomap_end
Date: Tue, 21 Jan 2025 19:25:04 -0800 [thread overview]
Message-ID: <20250122032504.GT3557553@frogsfrogsfrogs> (raw)
In-Reply-To: <20250120160907.1751-1-vulab@iscas.ac.cn>
On Tue, Jan 21, 2025 at 12:09:06AM +0800, Wentao Liang wrote:
> In xfs_dax_write_iomap_end(), directly return the result of
> xfs_reflink_cancel_cow_range() when !written, ensuring proper
> error propagation and improving code robustness.
>
> Fixes: ea6c49b784f0 ("xfs: support CoW in fsdax mode")
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
> fs/xfs/xfs_iomap.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c
> index 50fa3ef89f6c..d61460309a78 100644
> --- a/fs/xfs/xfs_iomap.c
> +++ b/fs/xfs/xfs_iomap.c
> @@ -976,10 +976,8 @@ xfs_dax_write_iomap_end(
> if (!xfs_is_cow_inode(ip))
> return 0;
>
> - if (!written) {
> - xfs_reflink_cancel_cow_range(ip, pos, length, true);
> - return 0;
> - }
> + if (!written)
> + return xfs_reflink_cancel_cow_range(ip, pos, length, true);
Ouch. Yeah, that's clearly wrong. Please add my tags:
Cc: <stable@vger.kernel.org> # v6.0
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
>
> return xfs_reflink_end_cow(ip, pos, written);
> }
> --
> 2.42.0.windows.2
>
prev parent reply other threads:[~2025-01-22 3:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 16:09 [PATCH] xfs: Propagate errors from xfs_reflink_cancel_cow_range in xfs_dax_write_iomap_end Wentao Liang
2025-01-22 3:25 ` 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=20250122032504.GT3557553@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=dchinner@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
--cc=yi.zhang@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