diff options
| author |   Baokun Li <libaokun1@huawei.com> | 2025-08-21 21:38:57 +0800 |
|---|---|---|
| committer |   Theodore Ts'o <tytso@mit.edu> | 2025-09-25 14:36:54 -0400 |
| commit | d8b90e6387a74bcb1714c8d1e6a782ff709de9a9 (patch) | |
| tree | 41d1845306f7700362ef282638e46dacad8ec717 /scripts/kernel-doc.py | |
| parent | ext4: replace min/max nesting with clamp() (diff) | |
| download | wireguard-linux-d8b90e6387a74bcb1714c8d1e6a782ff709de9a9.tar.xz wireguard-linux-d8b90e6387a74bcb1714c8d1e6a782ff709de9a9.zip | |
ext4: add ext4_sb_bread_nofail() helper function for ext4_free_branches()
The implicit __GFP_NOFAIL flag in ext4_sb_bread() was removed in commit
8a83ac54940d ("ext4: call bdev_getblk() from sb_getblk_gfp()"), meaning
the function can now fail under memory pressure.
Most callers of ext4_sb_bread() propagate the error to userspace and do not
remount the filesystem read-only. However, ext4_free_branches() handles
ext4_sb_bread() failure by remounting the filesystem read-only.
This implies that an ext3 filesystem (mounted via the ext4 driver) could be
forcibly remounted read-only due to a transient page allocation failure,
which is unacceptable.
To mitigate this, introduce a new helper function, ext4_sb_bread_nofail(),
which explicitly uses __GFP_NOFAIL, and use it in ext4_free_branches().
Fixes: 8a83ac54940d ("ext4: call bdev_getblk() from sb_getblk_gfp()")
Cc: stable@kernel.org
Signed-off-by: Baokun Li <libaokun1@huawei.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'scripts/kernel-doc.py')
0 files changed, 0 insertions, 0 deletions