diff options
author | Mingzhe Zou <mingzhe.zou@easystack.cn> | 2023-11-20 13:24:58 +0800 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2023-11-20 09:17:51 -0700 |
commit | 7cc47e64d3d69786a2711a4767e26b26ba63d7ed (patch) | |
tree | bcac5af501817c6f5d474a6ff251e763127cf333 | |
parent | 2c7f497ac274a14330208b18f6f734000868ebf9 (diff) | |
download | linux-7cc47e64d3d69786a2711a4767e26b26ba63d7ed.tar.gz linux-7cc47e64d3d69786a2711a4767e26b26ba63d7ed.tar.bz2 linux-7cc47e64d3d69786a2711a4767e26b26ba63d7ed.zip |
bcache: fixup init dirty data errors
We found that after long run, the dirty_data of the bcache device
will have errors. This error cannot be eliminated unless re-register.
We also found that reattach after detach, this error can accumulate.
In bch_sectors_dirty_init(), all inode <= d->id keys will be recounted
again. This is wrong, we only need to count the keys of the current
device.
Fixes: b144e45fc576 ("bcache: make bch_sectors_dirty_init() to be multithreaded")
Signed-off-by: Mingzhe Zou <mingzhe.zou@easystack.cn>
Cc: <stable@vger.kernel.org>
Signed-off-by: Coly Li <colyli@suse.de>
Link: https://lore.kernel.org/r/20231120052503.6122-6-colyli@suse.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
-rw-r--r-- | drivers/md/bcache/writeback.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/drivers/md/bcache/writeback.c b/drivers/md/bcache/writeback.c index c3e872e0a6f2..77fb72ac6b81 100644 --- a/drivers/md/bcache/writeback.c +++ b/drivers/md/bcache/writeback.c @@ -991,8 +991,11 @@ void bch_sectors_dirty_init(struct bcache_device *d) op.count = 0; for_each_key_filter(&c->root->keys, - k, &iter, bch_ptr_invalid) + k, &iter, bch_ptr_invalid) { + if (KEY_INODE(k) != op.inode) + continue; sectors_dirty_init_fn(&op.op, c->root, k); + } rw_unlock(0, c->root); return; |