aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/scsi/libsas/sas_init.c
diff options
context:
space:
mode:
authorHou Tao <[email protected]>2017-11-06 02:11:25 +0000
committerShaohua Li <[email protected]>2017-11-09 15:30:50 +0000
commit97f0eb9f0fec0563c1c796d95123e871b8bb65c0 (patch)
tree083bd0c08b7f665b762a84ff3142b3d62fbc4509 /drivers/scsi/libsas/sas_init.c
parentmd: be cautious about using ->curr_resync_completed for ->recovery_offset (diff)
downloadkernel-97f0eb9f0fec0563c1c796d95123e871b8bb65c0.tar.gz
kernel-97f0eb9f0fec0563c1c796d95123e871b8bb65c0.zip
md/bitmap: clear BITMAP_WRITE_ERROR bit before writing it to sb
For a RAID1 device using a file-based bitmap, if a bitmap write error occurs but the later writes succeed, it's possible both BITMAP_STALE and BITMAP_WRITE_ERROR bits will be written to the bitmap super block, the BITMAP_STALE bit will be handled properly and be cleared, but the BITMAP_WRITE_ERROR bit in sb->flags will make bitmap_create() to fail. So clear it to protect against the write failure-and-then-recovery case. Signed-off-by: Hou Tao <[email protected]> Signed-off-by: Shaohua Li <[email protected]>
Diffstat (limited to 'drivers/scsi/libsas/sas_init.c')
0 files changed, 0 insertions, 0 deletions