* [syzbot] possible deadlock in exfat_get_block
@ 2022-10-11 15:04 syzbot
2022-11-15 10:47 ` syzbot
2023-10-07 18:47 ` [syzbot] [exfat?] " syzbot
0 siblings, 2 replies; 3+ messages in thread
From: syzbot @ 2022-10-11 15:04 UTC (permalink / raw)
To: linkinjeon, linux-fsdevel, linux-kernel, sj1557.seo,
syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: bbed346d5a96 Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=16c2cd84880000
kernel config: https://syzkaller.appspot.com/x/.config?x=3a4a45d2d827c1e
dashboard link: https://syzkaller.appspot.com/bug?extid=247e66a2c3ea756332c7
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e8e91bc79312/disk-bbed346d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c1cb3fb3b77e/vmlinux-bbed346d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+247e66a2c3ea756332c7@syzkaller.appspotmail.com
======================================================
WARNING: possible circular locking dependency detected
6.0.0-rc7-syzkaller-18095-gbbed346d5a96 #0 Not tainted
------------------------------------------------------
syz-executor.4/3569 is trying to acquire lock:
ffff0000edcdd0e0 (&sbi->s_lock){+.+.}-{3:3}, at: exfat_get_block+0x6c/0x9ec fs/exfat/inode.c:282
but task is already holding lock:
ffff0001036340a0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
ffff0001036340a0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: page_cache_ra_unbounded+0x5c/0x338 mm/readahead.c:220
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (mapping.invalidate_lock#3){.+.+}-{3:3}:
down_read+0x5c/0x78 kernel/locking/rwsem.c:1499
filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
filemap_fault+0x104/0x804 mm/filemap.c:3112
__do_fault+0x60/0x358 mm/memory.c:4173
do_read_fault mm/memory.c:4518 [inline]
do_fault+0x338/0x550 mm/memory.c:4647
handle_pte_fault mm/memory.c:4911 [inline]
__handle_mm_fault mm/memory.c:5053 [inline]
handle_mm_fault+0x784/0xa40 mm/memory.c:5151
__do_page_fault arch/arm64/mm/fault.c:502 [inline]
do_page_fault+0x428/0x79c arch/arm64/mm/fault.c:602
do_translation_fault+0x78/0x194 arch/arm64/mm/fault.c:685
do_mem_abort+0x54/0x130 arch/arm64/mm/fault.c:821
el1_abort+0x3c/0x5c arch/arm64/kernel/entry-common.c:366
el1h_64_sync_handler+0x60/0xac arch/arm64/kernel/entry-common.c:426
el1h_64_sync+0x64/0x68 arch/arm64/kernel/entry.S:576
__arch_copy_from_user+0xb8/0x230 arch/arm64/lib/copy_template.S:110
copy_from_iter include/linux/uio.h:184 [inline]
copy_from_iter_full include/linux/uio.h:191 [inline]
memcpy_from_msg include/linux/skbuff.h:3959 [inline]
netlink_sendmsg+0x394/0x584 net/netlink/af_netlink.c:1906
sock_sendmsg_nosec net/socket.c:714 [inline]
sock_sendmsg net/socket.c:734 [inline]
sock_write_iter+0x140/0x1bc net/socket.c:1108
call_write_iter include/linux/fs.h:2187 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x2dc/0x46c fs/read_write.c:578
ksys_write+0xb4/0x160 fs/read_write.c:631
__do_sys_write fs/read_write.c:643 [inline]
__se_sys_write fs/read_write.c:640 [inline]
__arm64_sys_write+0x24/0x34 fs/read_write.c:640
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:636
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:654
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
-> #1 (&mm->mmap_lock){++++}-{3:3}:
__might_fault+0x7c/0xb4 mm/memory.c:5577
filldir64+0x1e4/0x56c fs/readdir.c:335
dir_emit_dot include/linux/fs.h:3547 [inline]
dir_emit_dots include/linux/fs.h:3558 [inline]
exfat_iterate+0xd8/0xcd8 fs/exfat/dir.c:231
iterate_dir+0x114/0x28c
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64 fs/readdir.c:354 [inline]
__arm64_sys_getdents64+0x80/0x204 fs/readdir.c:354
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:636
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:654
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
-> #0 (&sbi->s_lock){+.+.}-{3:3}:
check_prev_add kernel/locking/lockdep.c:3095 [inline]
check_prevs_add kernel/locking/lockdep.c:3214 [inline]
validate_chain kernel/locking/lockdep.c:3829 [inline]
__lock_acquire+0x1530/0x30a4 kernel/locking/lockdep.c:5053
lock_acquire+0x100/0x1f8 kernel/locking/lockdep.c:5666
__mutex_lock_common+0xd4/0xca8 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
exfat_get_block+0x6c/0x9ec fs/exfat/inode.c:282
do_mpage_readpage+0x474/0xd38 fs/mpage.c:208
mpage_readahead+0xf0/0x1b8 fs/mpage.c:361
exfat_readahead+0x28/0x38 fs/exfat/inode.c:345
read_pages+0x74/0x4a0 mm/readahead.c:158
page_cache_ra_unbounded+0x2cc/0x338 mm/readahead.c:263
do_page_cache_ra mm/readahead.c:293 [inline]
page_cache_ra_order+0x348/0x380 mm/readahead.c:550
ondemand_readahead+0x3cc/0x724 mm/readahead.c:672
page_cache_sync_ra+0xc4/0xdc mm/readahead.c:699
page_cache_sync_readahead include/linux/pagemap.h:1215 [inline]
filemap_get_pages+0x108/0x574 mm/filemap.c:2566
filemap_read+0x14c/0x6fc mm/filemap.c:2660
generic_file_read_iter+0x6c/0x25c mm/filemap.c:2806
__kernel_read+0x128/0x2cc fs/read_write.c:428
kernel_read+0xb8/0x150 fs/read_write.c:446
prepare_binprm fs/exec.c:1657 [inline]
search_binary_handler fs/exec.c:1711 [inline]
exec_binprm+0x1c8/0x670 fs/exec.c:1768
bprm_execve+0x334/0x404 fs/exec.c:1837
do_execveat_common+0x57c/0x5e4 fs/exec.c:1942
do_execve fs/exec.c:2016 [inline]
__do_sys_execve fs/exec.c:2092 [inline]
__se_sys_execve fs/exec.c:2087 [inline]
__arm64_sys_execve+0x44/0x58 fs/exec.c:2087
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:636
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:654
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
other info that might help us debug this:
Chain exists of:
&sbi->s_lock --> &mm->mmap_lock --> mapping.invalidate_lock#3
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(mapping.invalidate_lock#3);
lock(&mm->mmap_lock);
lock(mapping.invalidate_lock#3);
lock(&sbi->s_lock);
*** DEADLOCK ***
2 locks held by syz-executor.4/3569:
#0: ffff0000c659c3d0 (&sig->cred_guard_mutex){+.+.}-{3:3}, at: prepare_bprm_creds fs/exec.c:1470 [inline]
#0: ffff0000c659c3d0 (&sig->cred_guard_mutex){+.+.}-{3:3}, at: bprm_execve+0x48/0x404 fs/exec.c:1805
#1: ffff0001036340a0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
#1: ffff0001036340a0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: page_cache_ra_unbounded+0x5c/0x338 mm/readahead.c:220
stack backtrace:
CPU: 0 PID: 3569 Comm: syz-executor.4 Not tainted 6.0.0-rc7-syzkaller-18095-gbbed346d5a96 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
Call trace:
dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:156
show_stack+0x2c/0x54 arch/arm64/kernel/stacktrace.c:163
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x104/0x16c lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
print_circular_bug+0x2c4/0x2c8 kernel/locking/lockdep.c:2053
check_noncircular+0x14c/0x154 kernel/locking/lockdep.c:2175
check_prev_add kernel/locking/lockdep.c:3095 [inline]
check_prevs_add kernel/locking/lockdep.c:3214 [inline]
validate_chain kernel/locking/lockdep.c:3829 [inline]
__lock_acquire+0x1530/0x30a4 kernel/locking/lockdep.c:5053
lock_acquire+0x100/0x1f8 kernel/locking/lockdep.c:5666
__mutex_lock_common+0xd4/0xca8 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
exfat_get_block+0x6c/0x9ec fs/exfat/inode.c:282
do_mpage_readpage+0x474/0xd38 fs/mpage.c:208
mpage_readahead+0xf0/0x1b8 fs/mpage.c:361
exfat_readahead+0x28/0x38 fs/exfat/inode.c:345
read_pages+0x74/0x4a0 mm/readahead.c:158
page_cache_ra_unbounded+0x2cc/0x338 mm/readahead.c:263
do_page_cache_ra mm/readahead.c:293 [inline]
page_cache_ra_order+0x348/0x380 mm/readahead.c:550
ondemand_readahead+0x3cc/0x724 mm/readahead.c:672
page_cache_sync_ra+0xc4/0xdc mm/readahead.c:699
page_cache_sync_readahead include/linux/pagemap.h:1215 [inline]
filemap_get_pages+0x108/0x574 mm/filemap.c:2566
filemap_read+0x14c/0x6fc mm/filemap.c:2660
generic_file_read_iter+0x6c/0x25c mm/filemap.c:2806
__kernel_read+0x128/0x2cc fs/read_write.c:428
kernel_read+0xb8/0x150 fs/read_write.c:446
prepare_binprm fs/exec.c:1657 [inline]
search_binary_handler fs/exec.c:1711 [inline]
exec_binprm+0x1c8/0x670 fs/exec.c:1768
bprm_execve+0x334/0x404 fs/exec.c:1837
do_execveat_common+0x57c/0x5e4 fs/exec.c:1942
do_execve fs/exec.c:2016 [inline]
__do_sys_execve fs/exec.c:2092 [inline]
__se_sys_execve fs/exec.c:2087 [inline]
__arm64_sys_execve+0x44/0x58 fs/exec.c:2087
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:636
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:654
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [syzbot] possible deadlock in exfat_get_block
2022-10-11 15:04 [syzbot] possible deadlock in exfat_get_block syzbot
@ 2022-11-15 10:47 ` syzbot
2023-10-07 18:47 ` [syzbot] [exfat?] " syzbot
1 sibling, 0 replies; 3+ messages in thread
From: syzbot @ 2022-11-15 10:47 UTC (permalink / raw)
To: linkinjeon, linux-fsdevel, linux-kernel, sj1557.seo,
syzkaller-bugs
syzbot has found a reproducer for the following issue on:
HEAD commit: 9e4ce762f0e7 Merge branches 'for-next/acpi', 'for-next/asm..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=142ea0e9880000
kernel config: https://syzkaller.appspot.com/x/.config?x=20ffacc1ce1c99b5
dashboard link: https://syzkaller.appspot.com/bug?extid=247e66a2c3ea756332c7
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11cb6095880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13ecada5880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a70eb29add74/disk-9e4ce762.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/769d096516a8/vmlinux-9e4ce762.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9309615f51d5/Image-9e4ce762.gz.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/709895381a4a/mount_0.gz
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/b69a1a37527d/mount_3.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+247e66a2c3ea756332c7@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 4096
======================================================
WARNING: possible circular locking dependency detected
6.1.0-rc5-syzkaller-32254-g9e4ce762f0e7 #0 Not tainted
------------------------------------------------------
syz-executor410/3072 is trying to acquire lock:
ffff0000cb6210e0 (&sbi->s_lock){+.+.}-{3:3}, at: exfat_get_block+0x6c/0x9ec fs/exfat/inode.c:282
but task is already holding lock:
ffff0000ca589060 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
ffff0000ca589060 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: page_cache_ra_unbounded+0x5c/0x400 mm/readahead.c:226
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (mapping.invalidate_lock#3){.+.+}-{3:3}:
down_read+0x5c/0x78 kernel/locking/rwsem.c:1509
filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
filemap_fault+0x104/0x7fc mm/filemap.c:3127
__do_fault+0x60/0x358 mm/memory.c:4203
do_read_fault mm/memory.c:4554 [inline]
do_fault+0x338/0x550 mm/memory.c:4683
handle_pte_fault mm/memory.c:4955 [inline]
__handle_mm_fault mm/memory.c:5097 [inline]
handle_mm_fault+0x78c/0xa48 mm/memory.c:5218
__do_page_fault arch/arm64/mm/fault.c:506 [inline]
do_page_fault+0x428/0x79c arch/arm64/mm/fault.c:606
do_translation_fault+0x78/0x194 arch/arm64/mm/fault.c:689
do_mem_abort+0x54/0x130 arch/arm64/mm/fault.c:825
el1_abort+0x3c/0x5c arch/arm64/kernel/entry-common.c:367
el1h_64_sync_handler+0x60/0xac arch/arm64/kernel/entry-common.c:427
el1h_64_sync+0x64/0x68 arch/arm64/kernel/entry.S:579
do_strncpy_from_user lib/strncpy_from_user.c:41 [inline]
strncpy_from_user+0x1a8/0x3d8 lib/strncpy_from_user.c:139
getname_flags+0x84/0x278 fs/namei.c:150
getname+0x28/0x38 fs/namei.c:218
do_sys_openat2+0x78/0x22c fs/open.c:1304
do_sys_open fs/open.c:1326 [inline]
__do_sys_openat fs/open.c:1342 [inline]
__se_sys_openat fs/open.c:1337 [inline]
__arm64_sys_openat+0xb0/0xe0 fs/open.c:1337
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584
-> #1 (&mm->mmap_lock){++++}-{3:3}:
__might_fault+0x7c/0xb4 mm/memory.c:5646
filldir64+0x1e8/0x574 fs/readdir.c:335
dir_emit_dot include/linux/fs.h:3561 [inline]
dir_emit_dots include/linux/fs.h:3572 [inline]
exfat_iterate+0xd4/0xcb4 fs/exfat/dir.c:231
iterate_dir+0x114/0x28c
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64 fs/readdir.c:354 [inline]
__arm64_sys_getdents64+0x80/0x204 fs/readdir.c:354
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584
-> #0 (&sbi->s_lock){+.+.}-{3:3}:
check_prev_add kernel/locking/lockdep.c:3097 [inline]
check_prevs_add kernel/locking/lockdep.c:3216 [inline]
validate_chain kernel/locking/lockdep.c:3831 [inline]
__lock_acquire+0x1530/0x3084 kernel/locking/lockdep.c:5055
lock_acquire+0x100/0x1f8 kernel/locking/lockdep.c:5668
__mutex_lock_common+0xd4/0xca8 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
exfat_get_block+0x6c/0x9ec fs/exfat/inode.c:282
do_mpage_readpage+0x474/0xd38 fs/mpage.c:208
mpage_readahead+0xf0/0x1b8 fs/mpage.c:361
exfat_readahead+0x28/0x38 fs/exfat/inode.c:345
read_pages+0x8c/0x4f0 mm/readahead.c:161
page_cache_ra_unbounded+0x374/0x400 mm/readahead.c:270
do_page_cache_ra mm/readahead.c:300 [inline]
page_cache_ra_order+0x348/0x380 mm/readahead.c:560
ondemand_readahead+0x340/0x720 mm/readahead.c:682
page_cache_sync_ra+0xc4/0xdc mm/readahead.c:709
page_cache_sync_readahead include/linux/pagemap.h:1213 [inline]
filemap_get_pages+0x118/0x598 mm/filemap.c:2581
filemap_read+0x14c/0x6f4 mm/filemap.c:2675
generic_file_read_iter+0x6c/0x25c mm/filemap.c:2821
call_read_iter include/linux/fs.h:2185 [inline]
new_sync_read fs/read_write.c:389 [inline]
vfs_read+0x2d4/0x448 fs/read_write.c:470
ksys_read+0xb4/0x160 fs/read_write.c:613
__do_sys_read fs/read_write.c:623 [inline]
__se_sys_read fs/read_write.c:621 [inline]
__arm64_sys_read+0x24/0x34 fs/read_write.c:621
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584
other info that might help us debug this:
Chain exists of:
&sbi->s_lock --> &mm->mmap_lock --> mapping.invalidate_lock#3
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(mapping.invalidate_lock#3);
lock(&mm->mmap_lock);
lock(mapping.invalidate_lock#3);
lock(&sbi->s_lock);
*** DEADLOCK ***
1 lock held by syz-executor410/3072:
#0: ffff0000ca589060 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
#0: ffff0000ca589060 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: page_cache_ra_unbounded+0x5c/0x400 mm/readahead.c:226
stack backtrace:
CPU: 0 PID: 3072 Comm: syz-executor410 Not tainted 6.1.0-rc5-syzkaller-32254-g9e4ce762f0e7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
Call trace:
dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:156
show_stack+0x2c/0x54 arch/arm64/kernel/stacktrace.c:163
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x104/0x16c lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
print_circular_bug+0x2c4/0x2c8 kernel/locking/lockdep.c:2055
check_noncircular+0x14c/0x154 kernel/locking/lockdep.c:2177
check_prev_add kernel/locking/lockdep.c:3097 [inline]
check_prevs_add kernel/locking/lockdep.c:3216 [inline]
validate_chain kernel/locking/lockdep.c:3831 [inline]
__lock_acquire+0x1530/0x3084 kernel/locking/lockdep.c:5055
lock_acquire+0x100/0x1f8 kernel/locking/lockdep.c:5668
__mutex_lock_common+0xd4/0xca8 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
exfat_get_block+0x6c/0x9ec fs/exfat/inode.c:282
do_mpage_readpage+0x474/0xd38 fs/mpage.c:208
mpage_readahead+0xf0/0x1b8 fs/mpage.c:361
exfat_readahead+0x28/0x38 fs/exfat/inode.c:345
read_pages+0x8c/0x4f0 mm/readahead.c:161
page_cache_ra_unbounded+0x374/0x400 mm/readahead.c:270
do_page_cache_ra mm/readahead.c:300 [inline]
page_cache_ra_order+0x348/0x380 mm/readahead.c:560
ondemand_readahead+0x340/0x720 mm/readahead.c:682
page_cache_sync_ra+0xc4/0xdc mm/readahead.c:709
page_cache_sync_readahead include/linux/pagemap.h:1213 [inline]
filemap_get_pages+0x118/0x598 mm/filemap.c:2581
filemap_read+0x14c/0x6f4 mm/filemap.c:2675
generic_file_read_iter+0x6c/0x25c mm/filemap.c:2821
call_read_iter include/linux/fs.h:2185 [inline]
new_sync_read fs/read_write.c:389 [inline]
vfs_read+0x2d4/0x448 fs/read_write.c:470
ksys_read+0xb4/0x160 fs/read_write.c:613
__do_sys_read fs/read_write.c:623 [inline]
__se_sys_read fs/read_write.c:621 [inline]
__arm64_sys_read+0x24/0x34 fs/read_write.c:621
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [syzbot] [exfat?] possible deadlock in exfat_get_block
2022-10-11 15:04 [syzbot] possible deadlock in exfat_get_block syzbot
2022-11-15 10:47 ` syzbot
@ 2023-10-07 18:47 ` syzbot
1 sibling, 0 replies; 3+ messages in thread
From: syzbot @ 2023-10-07 18:47 UTC (permalink / raw)
To: hdanton, linkinjeon, linux-fsdevel, linux-kernel, sj1557.seo,
syzkaller-bugs
syzbot suspects this issue was fixed by commit:
commit ff84772fd45d486e4fc78c82e2f70ce5333543e6
Author: Sungjong Seo <sj1557.seo@samsung.com>
Date: Fri Jul 14 08:43:54 2023 +0000
exfat: release s_lock before calling dir_emit()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12f6bef1680000
start commit: 5d0c230f1de8 Linux 6.5-rc4
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=27a4e50cc5856a15
dashboard link: https://syzkaller.appspot.com/bug?extid=247e66a2c3ea756332c7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12532d91a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=105aae2ea80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: exfat: release s_lock before calling dir_emit()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-10-07 18:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-10-11 15:04 [syzbot] possible deadlock in exfat_get_block syzbot
2022-11-15 10:47 ` syzbot
2023-10-07 18:47 ` [syzbot] [exfat?] " syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).