From: Ken Raeburn Date: Tue, 6 Aug 2024 09:13:19 +0000 (-0400) Subject: dm vdo: remove bad check of bi_next field X-Git-Tag: v6.12-rc1~30^2~24 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=3a59b2ec2400017f7fcc5d794802ebc7f4187d22;p=thirdparty%2Fkernel%2Flinux.git dm vdo: remove bad check of bi_next field Remove this check to prevent spurious warning messages due to the behavior of other storage layers. This check was intended to make sure dm-vdo does not chain metadata bios together. However, vdo has no control over underlying storage layers, so the assertion is not always true. Signed-off-by: Ken Raeburn Signed-off-by: Matthew Sakai Signed-off-by: Mikulas Patocka --- diff --git a/drivers/md/dm-vdo/io-submitter.c b/drivers/md/dm-vdo/io-submitter.c index 9a3716bb3c05e..ab62abe18827b 100644 --- a/drivers/md/dm-vdo/io-submitter.c +++ b/drivers/md/dm-vdo/io-submitter.c @@ -346,7 +346,6 @@ void __submit_metadata_vio(struct vio *vio, physical_block_number_t physical, VDO_ASSERT_LOG_ONLY(!code->quiescent, "I/O not allowed in state %s", code->name); - VDO_ASSERT_LOG_ONLY(vio->bio->bi_next == NULL, "metadata bio has no next bio"); vdo_reset_completion(completion); completion->error_handler = error_handler;