From: Yongpeng Yang <yangyongpeng.storage@gmail.com>
To: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>,
axboe@kernel.dk, agk@redhat.com, snitzer@kernel.org,
mpatocka@redhat.com, song@kernel.org, yukuai@fnnas.com,
hch@lst.de, sagi@grimberg.me, kch@nvidia.com, jaegeuk@kernel.org,
chao@kernel.org, cem@kernel.org
Cc: dm-devel@lists.linux.dev, linux-raid@vger.kernel.org,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-block@vger.kernel.org, bpf@vger.kernel.org,
linux-xfs@vger.kernel.org,
Yongpeng Yang <yangyongpeng@xiaomi.com>
Subject: Re: [f2fs-dev] [PATCH V3 6/6] xfs: ignore discard return value
Date: Wed, 26 Nov 2025 10:37:10 +0800 [thread overview]
Message-ID: <b18c489f-d6ee-4986-94be-a9aade7d3a47@gmail.com> (raw)
In-Reply-To: <20251124234806.75216-7-ckulkarnilinux@gmail.com>
On 11/25/25 07:48, Chaitanya Kulkarni wrote:
> __blkdev_issue_discard() always returns 0, making all error checking
> in XFS discard functions dead code.
>
> Change xfs_discard_extents() return type to void, remove error variable,
> error checking, and error logging for the __blkdev_issue_discard() call
> in same function.
>
> Update xfs_trim_perag_extents() and xfs_trim_rtgroup_extents() to
> ignore the xfs_discard_extents() return value and error checking
> code.
>
> Update xfs_discard_rtdev_extents() to ignore __blkdev_issue_discard()
> return value and error checking code.
>
> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
> ---
> fs/xfs/xfs_discard.c | 27 +++++----------------------
> fs/xfs/xfs_discard.h | 2 +-
> 2 files changed, 6 insertions(+), 23 deletions(-)
>
> diff --git a/fs/xfs/xfs_discard.c b/fs/xfs/xfs_discard.c
> index 6917de832191..b6ffe4807a11 100644
> --- a/fs/xfs/xfs_discard.c
> +++ b/fs/xfs/xfs_discard.c
> @@ -108,7 +108,7 @@ xfs_discard_endio(
> * list. We plug and chain the bios so that we only need a single completion
> * call to clear all the busy extents once the discards are complete.
> */
> -int
> +void
> xfs_discard_extents(
> struct xfs_mount *mp,
> struct xfs_busy_extents *extents)
> @@ -116,7 +116,6 @@ xfs_discard_extents(
> struct xfs_extent_busy *busyp;
> struct bio *bio = NULL;
> struct blk_plug plug;
> - int error = 0;
>
> blk_start_plug(&plug);
> list_for_each_entry(busyp, &extents->extent_list, list) {
> @@ -126,18 +125,10 @@ xfs_discard_extents(
>
> trace_xfs_discard_extent(xg, busyp->bno, busyp->length);
>
> - error = __blkdev_issue_discard(btp->bt_bdev,
> + __blkdev_issue_discard(btp->bt_bdev,
> xfs_gbno_to_daddr(xg, busyp->bno),
> XFS_FSB_TO_BB(mp, busyp->length),
> GFP_KERNEL, &bio);
If blk_alloc_discard_bio() fails to allocate a bio inside
__blkdev_issue_discard(), this may lead to an invalid loop in
list_for_each_entry{}. Instead of using __blkdev_issue_discard(), how
about allocate and submit the discard bios explicitly in
list_for_each_entry{}?
Yongpeng,
> - if (error && error != -EOPNOTSUPP) {
> - xfs_info(mp,
> - "discard failed for extent [0x%llx,%u], error %d",
> - (unsigned long long)busyp->bno,
> - busyp->length,
> - error);
> - break;
> - }
> }
>
> if (bio) {
> @@ -148,8 +139,6 @@ xfs_discard_extents(
> xfs_discard_endio_work(&extents->endio_work);
> }
> blk_finish_plug(&plug);
> -
> - return error;
> }
>
> /*
> @@ -385,9 +374,7 @@ xfs_trim_perag_extents(
> * list after this function call, as it may have been freed by
> * the time control returns to us.
> */
> - error = xfs_discard_extents(pag_mount(pag), extents);
> - if (error)
> - break;
> + xfs_discard_extents(pag_mount(pag), extents);
>
> if (xfs_trim_should_stop())
> break;
> @@ -496,12 +483,10 @@ xfs_discard_rtdev_extents(
>
> trace_xfs_discard_rtextent(mp, busyp->bno, busyp->length);
>
> - error = __blkdev_issue_discard(bdev,
> + __blkdev_issue_discard(bdev,
> xfs_rtb_to_daddr(mp, busyp->bno),
> XFS_FSB_TO_BB(mp, busyp->length),
> GFP_NOFS, &bio);
> - if (error)
> - break;
> }
> xfs_discard_free_rtdev_extents(tr);
>
> @@ -741,9 +726,7 @@ xfs_trim_rtgroup_extents(
> * list after this function call, as it may have been freed by
> * the time control returns to us.
> */
> - error = xfs_discard_extents(rtg_mount(rtg), tr.extents);
> - if (error)
> - break;
> + xfs_discard_extents(rtg_mount(rtg), tr.extents);
>
> low = tr.restart_rtx;
> } while (!xfs_trim_should_stop() && low <= high);
> diff --git a/fs/xfs/xfs_discard.h b/fs/xfs/xfs_discard.h
> index 2b1a85223a56..8c5cc4af6a07 100644
> --- a/fs/xfs/xfs_discard.h
> +++ b/fs/xfs/xfs_discard.h
> @@ -6,7 +6,7 @@ struct fstrim_range;
> struct xfs_mount;
> struct xfs_busy_extents;
>
> -int xfs_discard_extents(struct xfs_mount *mp, struct xfs_busy_extents *busy);
> +void xfs_discard_extents(struct xfs_mount *mp, struct xfs_busy_extents *busy);
> int xfs_ioc_trim(struct xfs_mount *mp, struct fstrim_range __user *fstrim);
>
> #endif /* XFS_DISCARD_H */
next prev parent reply other threads:[~2025-11-26 2:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 23:48 [PATCH V3 0/6] block: ignore __blkdev_issue_discard() ret value Chaitanya Kulkarni
2025-11-24 23:48 ` [PATCH V3 1/6] block: ignore discard return value Chaitanya Kulkarni
2025-11-25 17:38 ` Jens Axboe
2025-11-25 19:09 ` Chaitanya Kulkarni
2025-11-25 19:19 ` Jens Axboe
2025-11-24 23:48 ` [PATCH V3 2/6] md: " Chaitanya Kulkarni
2025-11-24 23:48 ` [PATCH V3 3/6] dm: " Chaitanya Kulkarni
2025-11-24 23:48 ` [PATCH V3 4/6] nvmet: " Chaitanya Kulkarni
2025-11-26 10:14 ` [f2fs-dev] " Yongpeng Yang
2025-11-26 10:37 ` Christoph Hellwig
2025-11-24 23:48 ` [PATCH V3 5/6] f2fs: " Chaitanya Kulkarni
2025-11-25 1:10 ` Chao Yu
2025-11-25 6:33 ` Christoph Hellwig
2025-11-25 7:11 ` Chao Yu
2025-11-26 2:47 ` Chao Yu
2025-11-26 3:37 ` Chaitanya Kulkarni
2025-11-26 3:58 ` Chao Yu
2025-11-24 23:48 ` [PATCH V3 6/6] xfs: " Chaitanya Kulkarni
2025-11-26 2:37 ` Yongpeng Yang [this message]
2025-11-26 8:07 ` [f2fs-dev] " Chaitanya Kulkarni
2025-11-26 9:14 ` Yongpeng Yang
2025-11-26 9:48 ` Yongpeng Yang
2025-11-26 10:34 ` hch
2025-11-26 10:33 ` Christoph Hellwig
2025-11-25 13:20 ` [PATCH V3 0/6] block: ignore __blkdev_issue_discard() ret value Anuj gupta
2025-11-25 19:20 ` (subset) " Jens Axboe
2025-12-03 21:50 ` [f2fs-dev] " patchwork-bot+f2fs
2025-12-09 17:18 ` patchwork-bot+f2fs
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=b18c489f-d6ee-4986-94be-a9aade7d3a47@gmail.com \
--to=yangyongpeng.storage@gmail.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=cem@kernel.org \
--cc=chao@kernel.org \
--cc=ckulkarnilinux@gmail.com \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=sagi@grimberg.me \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=yangyongpeng@xiaomi.com \
--cc=yukuai@fnnas.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).