btrfs: zoned: don't force read-only on transient -EAGAIN from reloc merge
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:
btrfs: zoned: don't force read-only on transient -EAGAIN from reloc merge
On a zoned FS, btrfs_delayed_refs_rsv_refill() returns -EAGAIN whenever the over-committed metadata plus the zone_unusable bytes exceeds the usable size in a metadata block-group to avoid heavy over-commit of metadata and early ENOSPC in one transaction.
If this happens while doing reclaim, the transaction is getting aborted.
Treat -EAGAIN as a soft, retryable condition in case of block-group reclaim.
From the CVE record · Linux
On a zoned btrfs filesystem, a transient -EAGAIN during block-group reclaim can abort a transaction and force the filesystem read-only. The input does not describe an attacker, authentication requirements, or user interaction; the issue occurs under the specified metadata-space condition during reclaim.
Engineers running Linux kernels with zoned btrfs filesystems should check their systems; affected versions are not specified.