From: Christoph Hellwig Date: Mon, 18 Apr 2022 04:53:09 +0000 (+0200) Subject: raid5: don't set the discard_alignment queue limit X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=3d50d368c92ade2f98a3d0d28b842a57c35284e9;p=linux.git raid5: don't set the discard_alignment queue limit The discard_alignment queue limit is named a bit misleading means the offset into the block device at which the discard granularity starts. Setting it to the discard granularity as done by raid5 is mostly harmless but also useless. Signed-off-by: Christoph Hellwig Acked-by: Song Liu Reviewed-by: Martin K. Petersen Link: https://lore.kernel.org/r/20220418045314.360785-7-hch@lst.de Signed-off-by: Jens Axboe --- diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index 144ea077c2ede..39038fa8b1c80 100644 --- a/drivers/md/raid5.c +++ b/drivers/md/raid5.c @@ -7785,7 +7785,6 @@ static int raid5_run(struct mddev *mddev) */ stripe = stripe * PAGE_SIZE; stripe = roundup_pow_of_two(stripe); - mddev->queue->limits.discard_alignment = stripe; mddev->queue->limits.discard_granularity = stripe; blk_queue_max_write_zeroes_sectors(mddev->queue, 0);