Prevalent "Bad page state" errors with kernel 6.13.4

Ask Fedora
, , , ,
1

Running under kernel 6.13.4 (in Fedora 41 KDE), I’ve seen a lot of “Bad page state” errors in journalctl.

They happen in various processes, but especially “fuse mainloop”.

Checking my journalctl history, I had none of these before upgrading to 6.13.4 today, and none on my latest boot where I’ve gone back to 6.12.15.

I had a couple of crashes today which I suspect (but can’t be sure) these issues were implicated in. In both cases, a terminal command in Konsole hung, and over the next minute or so, all apps stopped responding.

This looks to be a regression in FUSE in kernel 6.13, particularly affecting flatpaks ([solved]BUG: Bad page state in process fuse mainloop - on kernel 6.13 - Help - NixOS Discourse).

From what I can tell (not an expert in kernel changelogs, so I might be wrong), a patch has been submitted ([PATCH] fuse: prevent folio use-after-free in readahead - Vlastimil Babka) but it isn’t in 6.13.4.

Arch has patched the kernel for this (Kernel 6.13 Crashes for Certain Operations Inside Flatpak / FUSE (#110) · Issues · Arch Linux / Packaging / Packages / linux · GitLab). Is there a possibility of Fedora doing something similar?

4 Likes
3

lwn.net has been covering issues with kernel side conversion to folios for FUSE that broke FUSE. You could read about the background there but need to be a subscriber: https://lwn.net/Articles/1008714/ it will be in the open in a few days.

I’m not sure which kernel version you need to get a working FUSE for Fedora.

1 Like
4

Interesting, this could be the reason behind my kernel crashes too!

Also always happen with various flatpak apps

1 Like
5

@boredsquirrel, I thought about linking this to OS slowed to a crawl too, but I couldn’t quite find a commonality between them except the kernel version. Perhaps that’s causal enough.

6
2 Likes