[v5.15] INFO: task hung in filename_create
0 views
Skip to first unread message
syzbot
Apr 15, 2024, 1:31:20 AMApr 15
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: fa3df276cd36 Linux 5.15.155
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=175209b3180000
kernel config: https://syzkaller.appspot.com/x/.config?x=fa45dfd65a261480
dashboard link: https://syzkaller.appspot.com/bug?extid=bf2e1952f5c999646687
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0dc19fc63531/disk-fa3df276.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fae4c89e243a/vmlinux-fa3df276.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a5c832fcb939/Image-fa3df276.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bf2e19...@syzkaller.appspotmail.com
INFO: task syz-executor.0:6236 blocked for more than 143 seconds.
Not tainted 5.15.155-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack: 0 pid: 6236 ppid: 5057 flags:0x0000000d
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
rwsem_down_write_slowpath+0xd94/0x17e0 kernel/locking/rwsem.c:1165
__down_write_common kernel/locking/rwsem.c:1292 [inline]
__down_write kernel/locking/rwsem.c:1301 [inline]
down_write_nested+0xec/0x130 kernel/locking/rwsem.c:1668
inode_lock_nested include/linux/fs.h:824 [inline]
filename_create+0x204/0x468 fs/namei.c:3835
do_mkdirat+0xac/0x610 fs/namei.c:4080
__do_sys_mkdirat fs/namei.c:4105 [inline]
__se_sys_mkdirat fs/namei.c:4103 [inline]
__arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4103
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor.0:6240 blocked for more than 143 seconds.
Not tainted 5.15.155-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack: 0 pid: 6240 ppid: 5057 flags:0x0000000d
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6518
rwsem_down_read_slowpath+0x5b0/0x988 kernel/locking/rwsem.c:1055
__down_read_common kernel/locking/rwsem.c:1239 [inline]
__down_read kernel/locking/rwsem.c:1252 [inline]
down_read+0x10c/0x398 kernel/locking/rwsem.c:1500
inode_lock_shared include/linux/fs.h:799 [inline]
open_last_lookups fs/namei.c:3531 [inline]
path_openat+0x630/0x26cc fs/namei.c:3739
do_filp_open+0x1a8/0x3b4 fs/namei.c:3769
do_sys_openat2+0x128/0x3d8 fs/open.c:1253
do_sys_open fs/open.c:1269 [inline]
__do_sys_openat fs/open.c:1285 [inline]
__se_sys_openat fs/open.c:1280 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1280
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor.0:6244 blocked for more than 143 seconds.
Not tainted 5.15.155-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack: 0 pid: 6244 ppid: 5057 flags:0x00000005
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6518
rwsem_down_read_slowpath+0x5b0/0x988 kernel/locking/rwsem.c:1055
__down_read_common kernel/locking/rwsem.c:1239 [inline]
__down_read kernel/locking/rwsem.c:1252 [inline]
down_read+0x10c/0x398 kernel/locking/rwsem.c:1500
inode_lock_shared include/linux/fs.h:799 [inline]
lookup_slow+0x50/0x84 fs/namei.c:1679
walk_component+0x394/0x4cc fs/namei.c:1976
lookup_last fs/namei.c:2431 [inline]
path_lookupat+0x13c/0x3d0 fs/namei.c:2455
filename_lookup+0x1c4/0x4c8 fs/namei.c:2484
user_path_at_empty+0x5c/0x1a4 fs/namei.c:2883
user_path_at include/linux/namei.h:57 [inline]
do_mount fs/namespace.c:3345 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount fs/namespace.c:3533 [inline]
__arm64_sys_mount+0x4dc/0x5e0 fs/namespace.c:3533
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffff800014b114e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:311
2 locks held by kworker/u4:3/285:
1 lock held by udevd/3584:
2 locks held by getty/3726:
#0: ffff0000d326b098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff800018e132e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1204 drivers/tty/n_tty.c:2158
3 locks held by kworker/1:4/4025:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001cae7c00 ((work_completion)(&map->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
#2: ffff800014b159f0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x54/0x4b0 kernel/rcu/tree.c:4039
2 locks held by kworker/u4:8/4844:
#0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001d357c00 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
2 locks held by syz-executor.0/6224:
1 lock held by syz-executor.0/6236:
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3835
1 lock held by syz-executor.0/6240:
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: open_last_lookups fs/namei.c:3531 [inline]
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: path_openat+0x630/0x26cc fs/namei.c:3739
1 lock held by syz-executor.0/6244:
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1679
2 locks held by syz-executor.2/6769:
1 lock held by syz-executor.2/6770:
#0: ffff000104108188 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
#0: ffff000104108188 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3835
1 lock held by syz-executor.2/6771:
#0: ffff000104108188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff000104108188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: open_last_lookups fs/namei.c:3531 [inline]
#0: ffff000104108188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: path_openat+0x630/0x26cc fs/namei.c:3739
1 lock held by syz-executor.2/6772:
#0: ffff000104108188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff000104108188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1679
2 locks held by syz-executor.3/7430:
1 lock held by syz-executor.3/7436:
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3835
1 lock held by syz-executor.3/7437:
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: open_last_lookups fs/namei.c:3531 [inline]
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: path_openat+0x630/0x26cc fs/namei.c:3739
1 lock held by syz-executor.3/7438:
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1679
1 lock held by syz-executor.1/7837:
1 lock held by syz-executor.1/7842:
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3835
1 lock held by syz-executor.1/7844:
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: open_last_lookups fs/namei.c:3531 [inline]
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: path_openat+0x630/0x26cc fs/namei.c:3739
1 lock held by syz-executor.1/7845:
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1679
1 lock held by udevd/8717:
1 lock held by syz-executor.3/8854:
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:475 [inline]
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1326 [inline]
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1621 [inline]
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x328/0x1e48 kernel/sched/core.c:6290
=============================================
---
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: fa3df276cd36 Linux 5.15.155
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=175209b3180000
kernel config: https://syzkaller.appspot.com/x/.config?x=fa45dfd65a261480
dashboard link: https://syzkaller.appspot.com/bug?extid=bf2e1952f5c999646687
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0dc19fc63531/disk-fa3df276.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fae4c89e243a/vmlinux-fa3df276.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a5c832fcb939/Image-fa3df276.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bf2e19...@syzkaller.appspotmail.com
INFO: task syz-executor.0:6236 blocked for more than 143 seconds.
Not tainted 5.15.155-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack: 0 pid: 6236 ppid: 5057 flags:0x0000000d
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
rwsem_down_write_slowpath+0xd94/0x17e0 kernel/locking/rwsem.c:1165
__down_write_common kernel/locking/rwsem.c:1292 [inline]
__down_write kernel/locking/rwsem.c:1301 [inline]
down_write_nested+0xec/0x130 kernel/locking/rwsem.c:1668
inode_lock_nested include/linux/fs.h:824 [inline]
filename_create+0x204/0x468 fs/namei.c:3835
do_mkdirat+0xac/0x610 fs/namei.c:4080
__do_sys_mkdirat fs/namei.c:4105 [inline]
__se_sys_mkdirat fs/namei.c:4103 [inline]
__arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4103
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor.0:6240 blocked for more than 143 seconds.
Not tainted 5.15.155-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack: 0 pid: 6240 ppid: 5057 flags:0x0000000d
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6518
rwsem_down_read_slowpath+0x5b0/0x988 kernel/locking/rwsem.c:1055
__down_read_common kernel/locking/rwsem.c:1239 [inline]
__down_read kernel/locking/rwsem.c:1252 [inline]
down_read+0x10c/0x398 kernel/locking/rwsem.c:1500
inode_lock_shared include/linux/fs.h:799 [inline]
open_last_lookups fs/namei.c:3531 [inline]
path_openat+0x630/0x26cc fs/namei.c:3739
do_filp_open+0x1a8/0x3b4 fs/namei.c:3769
do_sys_openat2+0x128/0x3d8 fs/open.c:1253
do_sys_open fs/open.c:1269 [inline]
__do_sys_openat fs/open.c:1285 [inline]
__se_sys_openat fs/open.c:1280 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1280
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor.0:6244 blocked for more than 143 seconds.
Not tainted 5.15.155-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack: 0 pid: 6244 ppid: 5057 flags:0x00000005
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6518
rwsem_down_read_slowpath+0x5b0/0x988 kernel/locking/rwsem.c:1055
__down_read_common kernel/locking/rwsem.c:1239 [inline]
__down_read kernel/locking/rwsem.c:1252 [inline]
down_read+0x10c/0x398 kernel/locking/rwsem.c:1500
inode_lock_shared include/linux/fs.h:799 [inline]
lookup_slow+0x50/0x84 fs/namei.c:1679
walk_component+0x394/0x4cc fs/namei.c:1976
lookup_last fs/namei.c:2431 [inline]
path_lookupat+0x13c/0x3d0 fs/namei.c:2455
filename_lookup+0x1c4/0x4c8 fs/namei.c:2484
user_path_at_empty+0x5c/0x1a4 fs/namei.c:2883
user_path_at include/linux/namei.h:57 [inline]
do_mount fs/namespace.c:3345 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount fs/namespace.c:3533 [inline]
__arm64_sys_mount+0x4dc/0x5e0 fs/namespace.c:3533
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffff800014b114e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:311
2 locks held by kworker/u4:3/285:
1 lock held by udevd/3584:
2 locks held by getty/3726:
#0: ffff0000d326b098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff800018e132e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1204 drivers/tty/n_tty.c:2158
3 locks held by kworker/1:4/4025:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001cae7c00 ((work_completion)(&map->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
#2: ffff800014b159f0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x54/0x4b0 kernel/rcu/tree.c:4039
2 locks held by kworker/u4:8/4844:
#0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001d357c00 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
2 locks held by syz-executor.0/6224:
1 lock held by syz-executor.0/6236:
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3835
1 lock held by syz-executor.0/6240:
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: open_last_lookups fs/namei.c:3531 [inline]
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: path_openat+0x630/0x26cc fs/namei.c:3739
1 lock held by syz-executor.0/6244:
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92ac188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1679
2 locks held by syz-executor.2/6769:
1 lock held by syz-executor.2/6770:
#0: ffff000104108188 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
#0: ffff000104108188 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3835
1 lock held by syz-executor.2/6771:
#0: ffff000104108188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff000104108188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: open_last_lookups fs/namei.c:3531 [inline]
#0: ffff000104108188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: path_openat+0x630/0x26cc fs/namei.c:3739
1 lock held by syz-executor.2/6772:
#0: ffff000104108188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff000104108188 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1679
2 locks held by syz-executor.3/7430:
1 lock held by syz-executor.3/7436:
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3835
1 lock held by syz-executor.3/7437:
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: open_last_lookups fs/namei.c:3531 [inline]
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: path_openat+0x630/0x26cc fs/namei.c:3739
1 lock held by syz-executor.3/7438:
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92ac6d0 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1679
1 lock held by syz-executor.1/7837:
1 lock held by syz-executor.1/7842:
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#20/1){+.+.}-{3:3}, at: filename_create+0x204/0x468 fs/namei.c:3835
1 lock held by syz-executor.1/7844:
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: open_last_lookups fs/namei.c:3531 [inline]
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: path_openat+0x630/0x26cc fs/namei.c:3739
1 lock held by syz-executor.1/7845:
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline]
#0: ffff0000e92acc18 (&type->i_mutex_dir_key#21){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1679
1 lock held by udevd/8717:
1 lock held by syz-executor.3/8854:
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:475 [inline]
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1326 [inline]
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1621 [inline]
#0: ffff0001b47fe958 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x328/0x1e48 kernel/sched/core.c:6290
=============================================
---
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 syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Apr 19, 2024, 2:22:21 PM (11 days ago) Apr 19
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 6741e066ec76 Linux 6.1.87
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=117f9ae7180000
kernel config: https://syzkaller.appspot.com/x/.config?x=3fc2f61bd0ae457
dashboard link: https://syzkaller.appspot.com/bug?extid=238b833d8da442497ae9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b606a22ddf4b/disk-6741e066.raw.xz
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/e31c21737449/vmlinux-6741e066.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee0cb8c049e9/bzImage-6741e066.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
INFO: task syz-executor.2:5501 blocked for more than 143 seconds.
Not tainted 6.1.87-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:28880 pid:5501 ppid:4956 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
rwsem_down_write_slowpath+0xea1/0x14b0 kernel/locking/rwsem.c:1189
inode_lock_nested include/linux/fs.h:793 [inline]
filename_create+0x25c/0x530 fs/namei.c:3878
do_mkdirat+0xba/0x360 fs/namei.c:4123
__do_sys_mkdirat fs/namei.c:4148 [inline]
__se_sys_mkdirat fs/namei.c:4146 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4146
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f54a787dea9
RSP: 002b:00007f54a86b80c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f54a79ac050 RCX: 00007f54a787dea9
RDX: 0000000000000000 RSI: 0000000020000080 RDI: ffffffffffffff9c
RBP: 00007f54a78ca4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f54a79ac050 R15: 00007ffc66561c28
</TASK>
INFO: task syz-executor.2:5502 blocked for more than 144 seconds.
Not tainted 6.1.87-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:27280 pid:5502 ppid:4956 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
rwsem_down_write_slowpath+0xea1/0x14b0 kernel/locking/rwsem.c:1189
inode_lock include/linux/fs.h:758 [inline]
open_last_lookups fs/namei.c:3549 [inline]
path_openat+0x7b6/0x2e60 fs/namei.c:3782
do_filp_open+0x230/0x480 fs/namei.c:3812
do_sys_openat2+0x13b/0x500 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1345
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f54a787dea9
RSP: 002b:00007f54a86970c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f54a79ac120 RCX: 00007f54a787dea9
RDX: 000000000000275a RSI: 0000000020000000 RDI: ffffffffffffff9c
RBP: 00007f54a78ca4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f54a79ac120 R15: 00007ffc66561c28
</TASK>
Showing all locks held in the system:
#0:
ffffffff8d12ae50 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d12b650 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8d12ac80 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6494
2 locks held by getty/3304:
#0: ffff88814b622098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2188
2 locks held by kworker/1:8/3614:
#0: ffff888012472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc9000483fd20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
3 locks held by kworker/u4:13/3707:
3 locks held by kworker/0:11/4324:
#0: ffff888012470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90012c37d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffffffff8d130278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#2: ffffffff8d130278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x360/0x930 kernel/rcu/tree_exp.h:962
2 locks held by syz-executor.2/5496:
2 locks held by syz-executor.2/5501:
#0: ffff888059348460 (sb_writers#27){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff8880515bc188 (&type->i_mutex_dir_key#23/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff8880515bc188 (&type->i_mutex_dir_key#23/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3878
2 locks held by syz-executor.2/5502:
#0: ffff888059348460 (sb_writers#27){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff8880515bc188 (&type->i_mutex_dir_key#24){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff8880515bc188 (&type->i_mutex_dir_key#24){+.+.}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#1: ffff8880515bc188 (&type->i_mutex_dir_key#24){+.+.}-{3:3}, at: path_openat+0x7b6/0x2e60 fs/namei.c:3782
1 lock held by syz-executor.4/7073:
#0: ffffffff8d130278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#0: ffffffff8d130278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x4f0/0x930 kernel/rcu/tree_exp.h:962
2 locks held by syz-executor.1/7710:
2 locks held by syz-executor.2/7729:
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.1.87-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf88/0xfd0 kernel/hung_task.c:377
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 3715 Comm: kworker/u4:17 Not tainted 6.1.87-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: bat_events batadv_purge_orig
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4748 [inline]
RIP: 0010:__lock_acquire+0x7e9/0x1f80 kernel/locking/lockdep.c:4999
Code: 50 0f b6 04 10 84 c0 0f 85 39 01 00 00 83 3d 9d af 5e 10 00 74 67 31 db 48 81 c3 b8 00 00 00 48 89 d8 48 c1 e8 03 0f b6 04 10 <84> c0 0f 85 c4 00 00 00 8b 03 41 38 c7 41 0f b6 cf 41 89 c7 44 0f
RSP: 0018:ffffc90004cf7880 EFLAGS: 00000802
RAX: 0000000000000000 RBX: ffffffff901e1e98 RCX: ffffffff816a717c
RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffffffff9049a2f8
RBP: ffff88807db6c6a8 R08: dffffc0000000000 R09: fffffbfff2093460
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000001
R13: ffff88807db6c6a8 R14: 0000000000000001 R15: 0000000000000004
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f57c0ff6d58 CR3: 000000007e41f000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
_raw_spin_lock_bh+0x31/0x40 kernel/locking/spinlock.c:178
spin_lock_bh include/linux/spinlock.h:356 [inline]
batadv_purge_orig_ref+0x1ba/0x1600 net/batman-adv/originator.c:1243
batadv_purge_orig+0x15/0x60 net/batman-adv/originator.c:1272
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Reply all
Reply to author
Forward
0 new messages