diff options
| author | Kent Overstreet <kent.overstreet@gmail.com> | 2021-02-10 03:54:40 +0300 |
|---|---|---|
| committer | Kent Overstreet <kent.overstreet@linux.dev> | 2023-10-23 00:08:53 +0300 |
| commit | eaf798317aa8fe3c8417ae1414c0b0bc58748881 (patch) | |
| tree | b9ca4748b89577166851aa63c10b2f896fd2c8ee | |
| parent | 6a16ad951ae4cb01dbfe73e8aa63045ee07e4581 (diff) | |
| download | linux-eaf798317aa8fe3c8417ae1414c0b0bc58748881.tar.xz | |
bcachefs: Fix for hash_redo_key() in fsck
It's possible we're calling hash_redo_key() because of a duplicate key -
easiest fix for that is to just not use BCH_HASH_SET_MUST_CREATE.
Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
| -rw-r--r-- | fs/bcachefs/fsck.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/bcachefs/fsck.c b/fs/bcachefs/fsck.c index df0f00f10bd7..c3e6137ffd75 100644 --- a/fs/bcachefs/fsck.c +++ b/fs/bcachefs/fsck.c @@ -193,7 +193,7 @@ static int hash_redo_key(const struct bch_hash_desc desc, bch2_trans_update(trans, k_iter, &delete, 0); return bch2_hash_set(trans, desc, &h->info, k_iter->pos.inode, - tmp, BCH_HASH_SET_MUST_CREATE); + tmp, 0); } static int fsck_hash_delete_at(struct btree_trans *trans, |