fs/writeback: skip AS_NO_DATA_INTEGRITY mappings in wait_sb_inodes()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fs/writeback: skip AS_NO_DATA_INTEGRITY mappings in wait_sb_inodes()
Above the while() loop in wait_sb_inodes(), we document that we must wait for all pages under writeback for data integrity. Consequently, if a mapping, like fuse, traditionally does not have data integrity semantics, there is no need to wait at all; we can simply skip these inodes.
This restores fuse back to prior behavior where syncs are no-ops. This fixes a user regression where if a system is running a faulty fuse server that does not reply to issued write requests, this causes wait_sb_inodes() to wait forever.
From the CVE record · Linux
The Linux kernel’s wait_sb_inodes() can wait indefinitely during sync when a faulty FUSE server does not respond to write requests. The input does not describe an attacker, authentication requirement, or user-interaction requirement.
Operators running the Linux kernel with FUSE should check their deployments; affected versions are not specified.