From: Hungyu Lin <dennylin0707@gmail.com>
To: axboe@kernel.dk
Cc: hch@infradead.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, dm-devel@lists.linux.dev,
mtsai@redhat.com, sashiko-bot@kernel.org, stable@vger.kernel.org,
dennylin0707@gmail.com
Subject: [PATCH v3] block: fix discard alignment for non-power-of-two granularities
Date: Tue, 3 Nov 2026 18:59:09 +0000 [thread overview]
Message-ID: <20261103185909.71843-1-dennylin0707@gmail.com> (raw)
bio_discard_limit() uses round_up() and round_down(), which require a
power-of-two alignment. However, discard_granularity need not be a power
of two. For example, dm-thin supports data block sizes that are arbitrary
multiples of 64 KiB and advertises the block size as its granularity.
With a 192 KiB granularity, discarding one complete block at offset
384 KiB is split into 128 KiB and 64 KiB bios. Neither covers a complete
thin block, so dm-thin ignores both and the mapping remains allocated.
Use div_u64_rem() to find the starting sector's remainder without
modifying the sector. Round the maximum bio size down with rounddown()
and subtract the remainder so that the next bio starts on a granularity
boundary. This handles non-power-of-two granularities and avoids a small
initial bio when a large discard starts at an unaligned sector.
When discard is unsupported or disabled, discard_granularity can be zero.
Return BIO_MAX_SECTORS in that case so the existing bio submission checks
can handle unsupported discard requests without dividing by zero.
Fixes: 9b15d109a6b2 ("block: improve discard bio alignment in __blkdev_issue_discard()")
Reported-by: Ming-Hung Tsai <mtsai@redhat.com>
Link: https://lore.kernel.org/r/CALjSBEvjbiGDVewuapWKhGDtaxZwcn4=22raUiBEOyj22rY7-g@mail.gmail.com
Suggested-by: Christoph Hellwig <hch@infradead.org>
Cc: stable@vger.kernel.org
Signed-off-by: Hungyu Lin <dennylin0707@gmail.com>
---
Changes in v3:
- Use div_u64_rem() instead of sector_div(), as suggested by Christoph
Hellwig, so the input sector is not modified.
- Subtract the starting-sector remainder from the rounded maximum size
instead of emitting a short initial bio, following Christoph's proposal.
- Include <linux/math64.h> explicitly and retain v2's zero-granularity guard.
Changes in v2:
- Handle zero discard_granularity before dividing, as pointed out by
Sashiko. Leave unsupported discard handling to the bio submission path.
v2: https://lore.kernel.org/r/20261026195131.46699-1-dennylin0707@gmail.com
block/blk-lib.c | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/block/blk-lib.c b/block/blk-lib.c
index 688bc67cbf7..e98aa483707 100644
--- a/block/blk-lib.c
+++ b/block/blk-lib.c
@@ -3,6 +3,7 @@
* Functions related to generic helpers functions
*/
#include <linux/kernel.h>
+#include <linux/math64.h>
#include <linux/module.h>
#include <linux/bio.h>
#include <linux/blkdev.h>
@@ -13,26 +14,25 @@
static sector_t bio_discard_limit(struct block_device *bdev, sector_t sector)
{
unsigned int discard_granularity = bdev_discard_granularity(bdev);
- sector_t granularity_aligned_sector;
+ u32 unaligned_sectors;
+
+ if (!discard_granularity)
+ return BIO_MAX_SECTORS;
if (bdev_is_partition(bdev))
sector += bdev->bd_start_sect;
- granularity_aligned_sector =
- round_up(sector, discard_granularity >> SECTOR_SHIFT);
-
- /*
- * Make sure subsequent bios start aligned to the discard granularity if
- * it needs to be split.
- */
- if (granularity_aligned_sector != sector)
- return granularity_aligned_sector - sector;
-
/*
- * Align the bio size to the discard granularity to make splitting the bio
- * at discard granularity boundaries easier in the driver if needed.
+ * Align the bio size to the discard granularity to make splitting the
+ * bio at discard granularity boundaries easier in the driver if needed.
+ *
+ * If the current sector is not aligned, shorten the range so that the
+ * next one is aligned.
*/
- return round_down(BIO_MAX_SIZE, discard_granularity) >> SECTOR_SHIFT;
+ div_u64_rem(sector, discard_granularity >> SECTOR_SHIFT,
+ &unaligned_sectors);
+ return (rounddown(BIO_MAX_SIZE, discard_granularity) >> SECTOR_SHIFT) -
+ unaligned_sectors;
}
struct bio *blk_alloc_discard_bio(struct block_device *bdev,
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.50.1 (Apple Git-155)
reply other threads:[~2026-11-03 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261103185909.71843-1-dennylin0707@gmail.com \
--to=dennylin0707@gmail.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtsai@redhat.com \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®