aboutsummaryrefslogtreecommitdiff
path: root/rust/helpers/task.c
diff options
context:
space:
mode:
authorYu Kuai <yukuai3@huawei.com>2024-10-31 11:31:10 +0800
committerSong Liu <song@kernel.org>2024-11-05 16:08:38 -0800
commit29967332ced51a15a22f11381eeebbc500ba1858 (patch)
tree59fe4d938ef9c97033b7ad2e528863def083e496 /rust/helpers/task.c
parent50e8274855e7ab5499ff8296e09802874a3f03b1 (diff)
downloadlinux-29967332ced51a15a22f11381eeebbc500ba1858.tar.gz
linux-29967332ced51a15a22f11381eeebbc500ba1858.tar.bz2
linux-29967332ced51a15a22f11381eeebbc500ba1858.zip
md: don't record new badblocks for faulty rdev
Faulty will be checked before issuing IO to the rdev, however, rdev can be faulty at any time, hence it's possible that rdev_set_badblocks() will be called for faulty rdev. In this case, mddev->sb_flags will be set and some other path can be blocked by updating super block. Since faulty rdev will not be accesed anymore, there is no need to record new babblocks for faulty rdev and forcing updating super block. Noted this is not a bugfix, just prevent updating superblock in some corner cases, and will help to slice a bug related to external metadata[1], testing also shows that devices are removed faster in the case IO error. [1] https://lore.kernel.org/all/f34452df-810b-48b2-a9b4-7f925699a9e7@linux.intel.com/ Signed-off-by: Yu Kuai <yukuai3@huawei.com> Tested-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com> Link: https://lore.kernel.org/r/20241031033114.3845582-4-yukuai1@huaweicloud.com Signed-off-by: Song Liu <song@kernel.org>
Diffstat (limited to 'rust/helpers/task.c')
0 files changed, 0 insertions, 0 deletions