bcachefs: Check for stale dirty pointer before reads

Browse source

Since we retry reads when we discover we read from a pointer that went
stale, if a dirty pointer is erroniously stale it would cause us to loop
retrying that read forever - unless we check before issuing the read,
while the btree is still locked, when we know that a dirty pointer
should never be stale.

This patch adds that check, along with printing some helpful debug info.

Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>

...

This commit is contained in:

Kent Overstreet 2022-02-15 00:06:59 -05:00 • committed by Kent Overstreet

parent fcf01959ea

commit eb331fe5a4

3 changed files with 54 additions and 14 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

fs/bcachefs/fs-io.c

View file

60

fs/bcachefs/io.c

View file

6

fs/bcachefs/move.c

View file