diff options
| author | Hou Tao | 2017-11-06 03:11:25 +0100 |
|---|---|---|
| committer | Shaohua Li | 2017-11-09 16:30:50 +0100 |
| commit | 97f0eb9f0fec0563c1c796d95123e871b8bb65c0 (patch) | |
| tree | 083bd0c08b7f665b762a84ff3142b3d62fbc4509 /drivers/md/bcache/debug.c | |
| parent | md: be cautious about using ->curr_resync_completed for ->recovery_offset (diff) | |
| download | kernel-qcow2-linux-97f0eb9f0fec0563c1c796d95123e871b8bb65c0.tar.gz kernel-qcow2-linux-97f0eb9f0fec0563c1c796d95123e871b8bb65c0.tar.xz kernel-qcow2-linux-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 <houtao1@huawei.com>
Signed-off-by: Shaohua Li <shli@fb.com>
Diffstat (limited to 'drivers/md/bcache/debug.c')
0 files changed, 0 insertions, 0 deletions