*** This bug is a duplicate of bug 2161222 ***
https://bugs.launchpad.net/bugs/2161222
Thanks for linking #2164537. After comparing the traces and upstream
changes, I am not sure these reports have the same root cause.
#2161222 fails synchronously in `iomap_write_end()` because
`iomap_inline_data_valid()` rejects an inline-data buffer whose
`kmemdup()` allocation is not page-aligned. Upstream addresses that with
commit 6b6fbad790ef (“ntfs3: Allocate iomap inline_data using
alloc_page”).
This #2164537 does not hit that exact bug. Its first failure is in the
writeback worker: `ntfs_writepages()` passes the positive internal value
`E_NTFS_NONRESIDENT` (556) to `mapping_set_error()`, while
`ntfs_resident_writepage()` deliberately skips `folio_unlock()` for that
value. The locked folio then strands both the writer and writeback
worker. Upstream commit 65bd5da999ef (“fs/ntfs3: fold resident writeback
into writepages loop”) changes this separate path and always unlocks the
folio.
Both failures involve resident NTFS3 writes and leave tasks unkillable,
but the failing paths and relevant upstream fixes differ. Could an
Ubuntu kernel maintainer please reassess the duplicate link?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2164537
Title:
NTFS3 resident writeback deadlock leaves writers permanently blocked
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-7.0/+bug/2164537/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
