mirror of
https://github.com/torvalds/linux.git
synced 2026-05-26 16:12:59 +02:00
bcachefs: Don't run triggers in fix_reflink_p_key()
It seems some users have reflink pointers which span many indirect extents, from a short window in time when merging of reflink pointers was allowed. Now, we're seeing transaction path overflows in fix_reflink_p(), the code path to clear out the reflink_p fields now used for front/back pad - but, we don't actually need to be running triggers in that path, which is an easy partial fix. Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>
This commit is contained in:
parent
d121172561
commit
6b3d8b8992
|
|
@ -2258,7 +2258,7 @@ static int fix_reflink_p_key(struct btree_trans *trans, struct btree_iter *iter)
|
|||
u->v.front_pad = 0;
|
||||
u->v.back_pad = 0;
|
||||
|
||||
return bch2_trans_update(trans, iter, &u->k_i, 0);
|
||||
return bch2_trans_update(trans, iter, &u->k_i, BTREE_TRIGGER_NORUN);
|
||||
}
|
||||
|
||||
static int fix_reflink_p(struct bch_fs *c)
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user