diff options
| author | Sungjong Seo <[email protected]> | 2024-05-31 10:14:44 +0000 |
|---|---|---|
| committer | Namjae Jeon <[email protected]> | 2024-07-15 12:44:28 +0000 |
| commit | 89fc548767a2155231128cb98726d6d2ea1256c9 (patch) | |
| tree | 389eb576a382449b2f8e2e1ac21fcbbbd5237234 /scripts/generate_rust_target.rs | |
| parent | exfat: handle idmapped mounts (diff) | |
| download | kernel-89fc548767a2155231128cb98726d6d2ea1256c9.tar.gz kernel-89fc548767a2155231128cb98726d6d2ea1256c9.zip | |
exfat: fix potential deadlock on __exfat_get_dentry_set
When accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array
is allocated in __exfat_get_entry_set. The problem is that the bh-array is
allocated with GFP_KERNEL. It does not make sense. In the following cases,
a deadlock for sbi->s_lock between the two processes may occur.
CPU0 CPU1
---- ----
kswapd
balance_pgdat
lock(fs_reclaim)
exfat_iterate
lock(&sbi->s_lock)
exfat_readdir
exfat_get_uniname_from_ext_entry
exfat_get_dentry_set
__exfat_get_dentry_set
kmalloc_array
...
lock(fs_reclaim)
...
evict
exfat_evict_inode
lock(&sbi->s_lock)
To fix this, let's allocate bh-array with GFP_NOFS.
Fixes: a3ff29a95fde ("exfat: support dynamic allocate bh for exfat_entry_set_cache")
Cc: [email protected] # v6.2+
Reported-by: [email protected]
Closes: https://lore.kernel.org/lkml/[email protected]
Signed-off-by: Sungjong Seo <[email protected]>
Signed-off-by: Namjae Jeon <[email protected]>
Diffstat (limited to 'scripts/generate_rust_target.rs')
0 files changed, 0 insertions, 0 deletions
