xfs: use a seprate member to track space availabe in the GC scatch buffer

Browse source

When scratch_head wraps back to 0 and scratch_tail is also 0 because no
I/O has completed yet, the ring buffer could be mistaken for empty.

Fix this by introducing a separate scratch_available member in
struct xfs_zone_gc_data.  This actually ends up simplifying the code as
well.

Reported-by: Chris Mason <clm@meta.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Hans Holmberg <hans.holmberg@wdc.com>
Signed-off-by: Carlos Maiolino <cem@kernel.org>

...

This commit is contained in:

Christoph Hellwig 2026-01-27 16:10:20 +01:00 • committed by Carlos Maiolino

parent 692243cac6

commit c17a1c0349

1 changed files with 9 additions and 16 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

25

fs/xfs/xfs_zone_gc.c

View file