diff options
| author | Ken Raeburn <[email protected]> | 2024-08-06 05:13:19 -0400 |
|---|---|---|
| committer | Mikulas Patocka <[email protected]> | 2024-08-21 13:05:56 +0200 |
| commit | 3a59b2ec2400017f7fcc5d794802ebc7f4187d22 (patch) | |
| tree | bca92e6ae0eaba12369657c3502ec125d1643432 | |
| parent | 0808ebf2f80b962e75741a41ced372a7116f1e26 (diff) | |
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 <[email protected]>
Signed-off-by: Matthew Sakai <[email protected]>
Signed-off-by: Mikulas Patocka <[email protected]>
| -rw-r--r-- | drivers/md/dm-vdo/io-submitter.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/md/dm-vdo/io-submitter.c b/drivers/md/dm-vdo/io-submitter.c index 9a3716bb3c05..ab62abe18827 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; |