diff options
author | 2025-07-12 19:31:49 -0400 | |
---|---|---|
committer | 2025-07-16 17:32:33 -0400 | |
commit | b4d6e204f892846b435ad5df89306a8ad56191f9 (patch) | |
tree | feb4818276e02e4afcbf4774184958261802978f | |
parent | bcachefs: io_read: remove from async obj list in rbio_done() (diff) | |
download | wireguard-linux-b4d6e204f892846b435ad5df89306a8ad56191f9.tar.xz wireguard-linux-b4d6e204f892846b435ad5df89306a8ad56191f9.zip |
bcachefs: Fix triggering of discard by the journal path
It becomes possible to do discards after a journal flush, which
naturally the journal code is reponsible for.
A prior refactoring seems to have broken this - which went unnoticed
because the foreground allocator path can also trigger discards.
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
-rw-r--r-- | fs/bcachefs/journal_io.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/bcachefs/journal_io.c b/fs/bcachefs/journal_io.c index dd3f3434c1b0..9e028dbcc3d0 100644 --- a/fs/bcachefs/journal_io.c +++ b/fs/bcachefs/journal_io.c @@ -1767,6 +1767,7 @@ static CLOSURE_CALLBACK(journal_write_done) closure_wake_up(&c->freelist_wait); bch2_reset_alloc_cursors(c); + do_discards = true; } j->seq_ondisk = seq; |