6 Jan
2026
6 Jan
'26
3:41 p.m.
On 1/6/26 16:21, Miklos Szeredi wrote:
On Tue, 6 Jan 2026 at 15:34, David Hildenbrand (Red Hat) david@kernel.org wrote:
I don't recall all the details, but I think that we might end up holding the folio lock forever while the fuse user space daemon is supposed to fill the page with data; anybody trying to lock the folio would similarly deadlock.
Right.
Maybe only compaction/migration is affected by that, hard to tell.
Can't imagine anything beyond actual I/O and folio logistics (reclaim/compaction) that would want to touch the page lock.
I assume the usual suspects, including mm/memory-failure.c.
memory_failure() not only contains a folio_wait_writeback() but also a folio_lock(), so twice the fun :)
--
Cheers
David