dm-io: report non-retryable errors separatedly
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.507.2.47.3In the Linux kernel, the following vulnerability has been resolved:
dm-io: report non-retryable errors separatedly
The error codes BLK_STS_NOTSUPP and BLK_STS_INVAL should not cause leg failure on dm-raid1. This patch changes the interface to dm-io, so that it reports two error bitmaps - error_bits and unsup_bits. The unsup_bit bitmap tracks BLK_STS_NOTSUPP or BLK_STS_INVAL errors, the error_bits bitmap tracks all the other errors.
dm-raid1 is changed so that it won't fail a leg if it receives an error in the unsup_bits bitmap.
This patch (with 62dc37a819a5) fixes misbehavior if the user uses unaligned bio vectors on dm-raid1.
From the CVE record · Linux
The Linux kernel's dm-io interface did not distinguish unsupported or invalid block-operation errors from other errors. When unaligned bio vectors are used on dm-raid1, this can cause a mirror leg to be failed incorrectly. The input does not describe a network attack or an authentication requirement.
Engineers running Linux kernel systems that use dm-raid1 should check whether their kernel includes the fix; affected versions are not specified.