From: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
To: 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: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
dm-devel@lists.linux.dev, linux-raid@vger.kernel.org,
linux-nvme@lists.infradead.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, bpf@vger.kernel.org,
Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
Subject: [PATCH V2 4/5] f2fs: ignore discard return value
Date: Sun, 23 Nov 2025 18:57:36 -0800 [thread overview]
Message-ID: <20251124025737.203571-5-ckulkarnilinux@gmail.com> (raw)
In-Reply-To: <20251124025737.203571-1-ckulkarnilinux@gmail.com>
__blkdev_issue_discard() always returns 0, making the error assignment
in __submit_discard_cmd() dead code.
Initialize err to 0 and remove the error assignment from the
__blkdev_issue_discard() call tp err. Move fault injection code into
already present if branch where err is set to -EIO.
This preserves the fault injection behavior while removing dead error
handling.
Signed-off-by: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
---
fs/f2fs/segment.c | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index b45eace879d7..3dbcfb9067e9 100644
--- a/fs/f2fs/segment.c
+++ b/fs/f2fs/segment.c
@@ -1343,15 +1343,9 @@ static int __submit_discard_cmd(struct f2fs_sb_info *sbi,
dc->di.len += len;
+ err = 0;
if (time_to_inject(sbi, FAULT_DISCARD)) {
err = -EIO;
- } else {
- err = __blkdev_issue_discard(bdev,
- SECTOR_FROM_BLOCK(start),
- SECTOR_FROM_BLOCK(len),
- GFP_NOFS, &bio);
- }
- if (err) {
spin_lock_irqsave(&dc->lock, flags);
if (dc->state == D_PARTIAL)
dc->state = D_SUBMIT;
@@ -1360,6 +1354,10 @@ static int __submit_discard_cmd(struct f2fs_sb_info *sbi,
break;
}
+ __blkdev_issue_discard(bdev,
+ SECTOR_FROM_BLOCK(start),
+ SECTOR_FROM_BLOCK(len),
+ GFP_NOFS, &bio);
f2fs_bug_on(sbi, !bio);
/*
--
2.40.0
next prev parent reply other threads:[~2025-11-24 2:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 2:57 [PATCH V2 0/5] block: ignore __blkdev_issue_discard() ret value Chaitanya Kulkarni
2025-11-24 2:57 ` [PATCH V2 1/5] block: ignore discard return value Chaitanya Kulkarni
2025-11-24 6:26 ` Christoph Hellwig
2025-11-24 7:50 ` Johannes Thumshirn
2025-11-24 12:57 ` Martin K. Petersen
2025-11-25 23:33 ` Wilfred Mallawa
2025-11-24 2:57 ` [PATCH V2 2/5] dm: " Chaitanya Kulkarni
2025-11-24 6:24 ` Yu Kuai
2025-11-24 6:27 ` Christoph Hellwig
2025-11-24 7:53 ` Johannes Thumshirn
2025-11-24 12:59 ` Martin K. Petersen
2025-11-25 23:41 ` Wilfred Mallawa
2025-11-26 9:26 ` Damien Le Moal
2025-11-24 2:57 ` [PATCH V2 3/5] nvmet: " Chaitanya Kulkarni
2025-11-24 6:28 ` Christoph Hellwig
2025-11-24 7:54 ` Johannes Thumshirn
2025-11-24 13:03 ` Martin K. Petersen
2025-11-24 2:57 ` Chaitanya Kulkarni [this message]
2025-11-24 6:30 ` [PATCH V2 4/5] f2fs: " Christoph Hellwig
2025-11-24 7:56 ` Johannes Thumshirn
2025-11-24 12:58 ` Martin K. Petersen
2025-11-24 2:57 ` [PATCH V2 5/5] xfs: " Chaitanya Kulkarni
2025-11-24 6:31 ` Christoph Hellwig
2025-11-24 7:57 ` Johannes Thumshirn
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=20251124025737.203571-5-ckulkarnilinux@gmail.com \
--to=ckulkarnilinux@gmail.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=cem@kernel.org \
--cc=chao@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--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=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