summaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-strncpy.c
diff options
context:
space:
mode:
authorKent Overstreet <kent.overstreet@linux.dev>2025-04-02 19:23:25 +0300
committerKent Overstreet <kent.overstreet@linux.dev>2025-04-03 19:11:43 +0300
commit77ad1df82b9e8d169e3ec9ee8b7caabfa45872ce (patch)
tree22247f54e0995311caa7135594706ae3d8e13a73 /lib/test_fortify/write_overflow-strncpy.c
parent2581f89ac8d7174fda975523ae6c2bdc8ad62144 (diff)
downloadlinux-77ad1df82b9e8d169e3ec9ee8b7caabfa45872ce.tar.xz
bcachefs: Fix "journal stuck" during recovery
If we crash when the journal pin fifo is completely full - i.e. we're at the maximum number of dirty journal entries - that may put us in a sticky situation in recovery, as journal replay will need to be able to open new journal entries in order to get going. bch2_fs_journal_start() already had provisions for resizing the journal pin fifo if needed, but it needs a fudge factor to ensure there's room for journal replay. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy.c')
0 files changed, 0 insertions, 0 deletions