diff options
| author | Guoqing Jiang <[email protected]> | 2021-10-04 23:34:48 +0800 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2021-10-18 14:50:25 -0600 |
| commit | fd3b6975e9c11c4fa00965f82a0bfbb3b7b44101 (patch) | |
| tree | 5eb2e9695bdee90a4a360abc7160dd1100505b07 /tools/perf/scripts/python/check-perf-trace.py | |
| parent | 7ad1069166c0ccdd572d27e01cc7f7f84477df1e (diff) | |
md/raid1: only allocate write behind bio for WriteMostly device
Commit 6607cd319b6b91bff94e90f798a61c031650b514 ("raid1: ensure write
behind bio has less than BIO_MAX_VECS sectors") tried to guarantee the
size of behind bio is not bigger than BIO_MAX_VECS sectors.
Unfortunately the same calltrace still could happen since an array could
enable write-behind without write mostly device.
To match the manpage of mdadm (which says "write-behind is only attempted
on drives marked as write-mostly"), we need to check WriteMostly flag to
avoid such unexpected behavior.
[1]. https://bugzilla.kernel.org/show_bug.cgi?id=213181#c25
Cc: [email protected] # v5.12+
Cc: Jens Stutte <[email protected]>
Reported-by: Jens Stutte <[email protected]>
Signed-off-by: Guoqing Jiang <[email protected]>
Signed-off-by: Song Liu <[email protected]>
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions