On Mon, 18 Apr 2022 06:53:03 +0200, Christoph Hellwig wrote:
> the somewhat confusing name of the discard_alignment queue limit, that
> really is an offset for the discard granularity mislead a lot of driver
> authors to set it to an incorrect value. This series tries to fix up
> all these cases.
>
> Diffstat:
> arch/um/drivers/ubd_kern.c |1 -
> drivers/block/loop.c |1 -
> drivers/block/nbd.c|3 ---
> drivers/block/null_blk/main.c |1 -
> drivers/block/rnbd/rnbd-srv-dev.h |2 +-
> drivers/block/virtio_blk.c |7 ---
> drivers/block/xen-blkback/xenbus.c |4 ++--
> drivers/md/dm-zoned-target.c |2 +-
> drivers/md/raid5.c |1 -
> drivers/nvme/host/core.c |1 -
> drivers/s390/block/dasd_fba.c |1 -
> 11 files changed, 8 insertions(+), 16 deletions(-)
>
> [...]
Applied, thanks!
[01/11] ubd: don't set the discard_alignment queue limit
commit: 07c6e92a8478770a7302f7dde72f03a5465901bd
[02/11] nbd: don't set the discard_alignment queue limit
commit: 4a04d517c56e0616c6f69afc226ee2691e543712
[03/11] null_blk: don't set the discard_alignment queue limit
commit: fb749a87f4536d2fa86ea135ae4eff1072903438
[04/11] virtio_blk: fix the discard_granularity and discard_alignment queue
limits
commit: 62952cc5bccd89b76d710de1d0b43244af0f2903
[05/11] dm-zoned: don't set the discard_alignment queue limit
commit: 44d583702f4429763c558624fac763650a1f05bf
[06/11] raid5: don't set the discard_alignment queue limit
commit: 3d50d368c92ade2f98a3d0d28b842a57c35284e9
[07/11] dasd: don't set the discard_alignment queue limit
commit: c3f765299632727fa5ea5a0acf118665227a4f1a
[08/11] loop: remove a spurious clear of discard_alignment
commit: 4418bfd8fb9602d9cd8747c3ad52fdbaa02e2ffd
[09/11] nvme: remove a spurious clear of discard_alignment
commit: 4e7f0ece41e1be8f876f320a0972a715daec0a50
[10/11] rnbd-srv: use bdev_discard_alignment
commit: 18292faa89d2bff3bdd33ab9c065f45fb6710e47
[11/11] xen-blkback: use bdev_discard_alignment
commit: c899b23533866910c90ef4386b501af50270d320
Best regards,
--
Jens Axboe
