On Fri, 11 Jul 2025 18:32:03 +0200, Jan Kara wrote:
> Syzbot came up with a reproducer where a loop device block size is
> changed underneath a mounted filesystem. This causes a mismatch between
> the block device block size and the block size stored in the superblock
> causing confusion in various places such as fs/buffer.c. The particular
> issue triggered by syzbot was a warning in __getblk_slow() due to
> requested buffer size not matching block device block size.
>
> [...]
Applied, thanks!
[1/1] loop: Avoid updating block size under exclusive owner
commit: 7e49538288e523427beedd26993d446afef1a6fb
Best regards,
--
Jens Axboe
