[v6.1] INFO: task hung in filename_create (2)
4 views
Skip to first unread message
syzbot
Nov 26, 2024, 2:48:27 AM11/26/24
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16f90f5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=5516a02be29a5649
dashboard link: https://syzkaller.appspot.com/bug?extid=4337a9544ad38c676780
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/19f991f20183/disk-e4d90d63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/61eb5f055f38/vmlinux-e4d90d63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0ddd97416681/bzImage-e4d90d63.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4337a9...@syzkaller.appspotmail.com
INFO: task syz.0.527:6562 blocked for more than 144 seconds.
Not tainted 6.1.119-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.527 state:D stack:28552 pid:6562 ppid:4248 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__do_sys_mkdirat fs/namei.c:4146 [inline]
__se_sys_mkdirat fs/namei.c:4144 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4144
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:0x7fb33e77e819
RSP: 002b:00007fb33e5de038 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fb33e936080 RCX: 00007fb33e77e819
RDX: 0000000000000000 RSI: 0000000020000000 RDI: ffffffffffffff9c
RBP: 00007fb33e7f175e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fb33e936080 R15: 00007ffe6ae06de8
</TASK>
INFO: task syz.0.527:6564 blocked for more than 145 seconds.
Not tainted 6.1.119-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.527 state:D stack:28080 pid:6564 ppid:4248 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
rwsem_down_read_slowpath kernel/locking/rwsem.c:1094 [inline]
__down_read_common kernel/locking/rwsem.c:1261 [inline]
__down_read kernel/locking/rwsem.c:1274 [inline]
down_read+0x6ff/0xa30 kernel/locking/rwsem.c:1522
inode_lock_shared include/linux/fs.h:768 [inline]
open_last_lookups fs/namei.c:3549 [inline]
path_openat+0x7a7/0x2e60 fs/namei.c:3780
do_filp_open+0x230/0x480 fs/namei.c:3810
do_sys_openat2+0x13b/0x4f0 fs/open.c:1318
__do_sys_openat2 fs/open.c:1377 [inline]
__se_sys_openat2+0x251/0x2f0 fs/open.c:1353
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:0x7fb33e77e819
RSP: 002b:00007fb33e5bd038 EFLAGS: 00000246 ORIG_RAX: 00000000000001b5
RAX: ffffffffffffffda RBX: 00007fb33e936160 RCX: 00007fb33e77e819
RDX: 0000000020000080 RSI: 00000000200000c0 RDI: ffffffffffffff9c
RBP: 00007fb33e7f175e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000018 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fb33e936160 R15: 00007ffe6ae06de8
</TASK>
Showing all locks held in the system:
4 locks held by kworker/u4:1/11:
#0: ffff888017e16938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90000107d20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffffffff8e4fe3d0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf1/0xb60 net/core/net_namespace.c:566
#3: ffffffff8e50a768 (rtnl_mutex){+.+.}-{3:3}, at: ip6_tnl_exit_batch_net+0xc0/0x5e0 net/ipv6/ip6_tunnel.c:2294
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d32b110 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d32b910 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/27:
#0: ffffffff8d32af40 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8d32af40 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8d32af40 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6510
1 lock held by dhcpcd/3916:
#0: ffffffff8e50a768 (rtnl_mutex){+.+.}-{3:3}, at: devinet_ioctl+0x2a5/0x1ae0 net/ipv4/devinet.c:1081
2 locks held by getty/4006:
#0: ffff88807e690098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000325e2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2198
2 locks held by kworker/1:6/4597:
#0: ffff888017c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90005107d20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
2 locks held by kworker/u4:19/5120:
#0: ffff888017c79138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90003347d20 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
2 locks held by syz.0.527/6550:
2 locks held by syz.0.527/6562:
#0: ffff88802f7d0460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff888055ce4a38 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff888055ce4a38 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
1 lock held by syz.0.527/6564:
#0: ffff888055ce4a38 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff888055ce4a38 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#0: ffff888055ce4a38 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: path_openat+0x7a7/0x2e60 fs/namei.c:3780
1 lock held by syz-executor/7980:
#0: ffffffff8e50a768 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8e50a768 (rtnl_mutex){+.+.}-{3:3}, at: __rtnl_newlink net/core/rtnetlink.c:3629 [inline]
#0: ffffffff8e50a768 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_newlink+0xadf/0x2050 net/core/rtnetlink.c:3652
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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+0x1ae/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:295
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:111 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:567
---
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: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16f90f5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=5516a02be29a5649
dashboard link: https://syzkaller.appspot.com/bug?extid=4337a9544ad38c676780
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/19f991f20183/disk-e4d90d63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/61eb5f055f38/vmlinux-e4d90d63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0ddd97416681/bzImage-e4d90d63.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4337a9...@syzkaller.appspotmail.com
INFO: task syz.0.527:6562 blocked for more than 144 seconds.
Not tainted 6.1.119-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.527 state:D stack:28552 pid:6562 ppid:4248 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__do_sys_mkdirat fs/namei.c:4146 [inline]
__se_sys_mkdirat fs/namei.c:4144 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4144
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:0x7fb33e77e819
RSP: 002b:00007fb33e5de038 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fb33e936080 RCX: 00007fb33e77e819
RDX: 0000000000000000 RSI: 0000000020000000 RDI: ffffffffffffff9c
RBP: 00007fb33e7f175e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fb33e936080 R15: 00007ffe6ae06de8
</TASK>
INFO: task syz.0.527:6564 blocked for more than 145 seconds.
Not tainted 6.1.119-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.527 state:D stack:28080 pid:6564 ppid:4248 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
rwsem_down_read_slowpath kernel/locking/rwsem.c:1094 [inline]
__down_read_common kernel/locking/rwsem.c:1261 [inline]
__down_read kernel/locking/rwsem.c:1274 [inline]
down_read+0x6ff/0xa30 kernel/locking/rwsem.c:1522
inode_lock_shared include/linux/fs.h:768 [inline]
open_last_lookups fs/namei.c:3549 [inline]
path_openat+0x7a7/0x2e60 fs/namei.c:3780
do_filp_open+0x230/0x480 fs/namei.c:3810
do_sys_openat2+0x13b/0x4f0 fs/open.c:1318
__do_sys_openat2 fs/open.c:1377 [inline]
__se_sys_openat2+0x251/0x2f0 fs/open.c:1353
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:0x7fb33e77e819
RSP: 002b:00007fb33e5bd038 EFLAGS: 00000246 ORIG_RAX: 00000000000001b5
RAX: ffffffffffffffda RBX: 00007fb33e936160 RCX: 00007fb33e77e819
RDX: 0000000020000080 RSI: 00000000200000c0 RDI: ffffffffffffff9c
RBP: 00007fb33e7f175e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000018 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fb33e936160 R15: 00007ffe6ae06de8
</TASK>
Showing all locks held in the system:
4 locks held by kworker/u4:1/11:
#0: ffff888017e16938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90000107d20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffffffff8e4fe3d0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf1/0xb60 net/core/net_namespace.c:566
#3: ffffffff8e50a768 (rtnl_mutex){+.+.}-{3:3}, at: ip6_tnl_exit_batch_net+0xc0/0x5e0 net/ipv6/ip6_tunnel.c:2294
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d32b110 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d32b910 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/27:
#0: ffffffff8d32af40 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8d32af40 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8d32af40 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6510
1 lock held by dhcpcd/3916:
#0: ffffffff8e50a768 (rtnl_mutex){+.+.}-{3:3}, at: devinet_ioctl+0x2a5/0x1ae0 net/ipv4/devinet.c:1081
2 locks held by getty/4006:
#0: ffff88807e690098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000325e2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2198
2 locks held by kworker/1:6/4597:
#0: ffff888017c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90005107d20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
2 locks held by kworker/u4:19/5120:
#0: ffff888017c79138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90003347d20 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
2 locks held by syz.0.527/6550:
2 locks held by syz.0.527/6562:
#0: ffff88802f7d0460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff888055ce4a38 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff888055ce4a38 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
1 lock held by syz.0.527/6564:
#0: ffff888055ce4a38 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff888055ce4a38 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: open_last_lookups fs/namei.c:3549 [inline]
#0: ffff888055ce4a38 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: path_openat+0x7a7/0x2e60 fs/namei.c:3780
1 lock held by syz-executor/7980:
#0: ffffffff8e50a768 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8e50a768 (rtnl_mutex){+.+.}-{3:3}, at: __rtnl_newlink net/core/rtnetlink.c:3629 [inline]
#0: ffffffff8e50a768 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_newlink+0xadf/0x2050 net/core/rtnetlink.c:3652
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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+0x1ae/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:295
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:111 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:567
---
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
Dec 30, 2024, 10:23:22 PM12/30/24
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 563edd786f0a Linux 6.1.122
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10d3eaf8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b70d05b26edc7515
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d3eaf8580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f111015ce9f/disk-563edd78.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/821c260b7642/vmlinux-563edd78.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9fba8f114c58/bzImage-563edd78.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/20b8946b3c25/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4337a9...@syzkaller.appspotmail.com
INFO: task syz-executor361:4266 blocked for more than 143 seconds.
Tainted: G W 6.1.122-syzkaller #0
__se_sys_mkdir fs/namei.c:4149 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4149
RSP: 002b:00007f9269088228 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f926917e6b8 RCX: 00007f92690ecd89
RDX: 00007f92690c6316 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f926917e6b0 R08: 00007ffc82c71207 R09: 00007f92690886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f926917e6bc
R13: 0031656c69662f2e R14: 00007f9269141160 R15: 00007ffc82c71208
</TASK>
INFO: task syz-executor361:4265 blocked for more than 144 seconds.
Tainted: G W 6.1.122-syzkaller #0
__se_sys_mkdir fs/namei.c:4149 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4149
RSP: 002b:00007f9269088228 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f926917e6b8 RCX: 00007f92690ecd89
RDX: 00007f92690c6316 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f926917e6b0 R08: 00007ffc82c71207 R09: 00007f92690886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f926917e6bc
R13: 0031656c69662f2e R14: 00007f9269141160 R15: 00007ffc82c71208
</TASK>
INFO: task syz-executor361:4263 blocked for more than 145 seconds.
Tainted: G W 6.1.122-syzkaller #0
__se_sys_mkdir fs/namei.c:4149 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4149
RSP: 002b:00007f9269088228 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f926917e6b8 RCX: 00007f92690ecd89
RDX: 00007f92690c6316 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f926917e6b0 R08: 00007ffc82c71207 R09: 00007f92690886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f926917e6bc
R13: 0031656c69662f2e R14: 00007f9269141160 R15: 00007ffc82c71208
</TASK>
INFO: task syz-executor361:4264 blocked for more than 145 seconds.
Tainted: G W 6.1.122-syzkaller #0
__se_sys_mkdir fs/namei.c:4149 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4149
RSP: 002b:00007f9269088228 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f926917e6b8 RCX: 00007f92690ecd89
RDX: 00007f92690c6316 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f926917e6b0 R08: 00007ffc82c71207 R09: 00007f92690886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f926917e6bc
R13: 0031656c69662f2e R14: 00007f9269141160 R15: 00007ffc82c71208
</TASK>
INFO: task syz-executor361:4267 blocked for more than 146 seconds.
Tainted: G W 6.1.122-syzkaller #0
__se_sys_mkdir fs/namei.c:4149 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4149
RSP: 002b:00007f9269088228 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f926917e6b8 RCX: 00007f92690ecd89
RDX: 00007f92690c6316 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f926917e6b0 R08: 00007ffc82c71207 R09: 00007f92690886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f926917e6bc
R13: 0031656c69662f2e R14: 00007f9269141160 R15: 00007ffc82c71208
2 locks held by kworker/1:0/22:
#0: ffffffff8d32b0c0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8d32b0c0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6510
1 lock held by kswapd0/83:
2 locks held by getty/4012:
#0: ffff888030d4b098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
2 locks held by syz-executor361/4266:
#0: ffff888079844460 (sb_writers#10){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88806e0886d0 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff88806e0886d0 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
2 locks held by syz-executor361/4260:
2 locks held by syz-executor361/4265:
#0: ffff8880302f2460 (sb_writers#10){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88806e0586d0 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff88806e0586d0 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
2 locks held by syz-executor361/4257:
2 locks held by syz-executor361/4263:
#0: ffff888030e78460 (sb_writers#10){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88806e088188 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff88806e088188 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
3 locks held by syz-executor361/4262:
2 locks held by syz-executor361/4264:
#0: ffff8880736dc460 (sb_writers#10){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88806e088c18 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff88806e088c18 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
5 locks held by syz-executor361/4258:
2 locks held by syz-executor361/4267:
#0: ffff888029cf4460 (sb_writers#10){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88806e058188 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff88806e058188 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
2 locks held by dhcpcd/4292:
#0: ffff8880244f8130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1750 [inline]
#0: ffff8880244f8130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x32/0xd00 net/packet/af_packet.c:3263
#1: ffffffff8d3306f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#1: ffffffff8d3306f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x360/0x930 kernel/rcu/tree_exp.h:962
1 lock held by dhcpcd/4293:
#0: ffff88807721c130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1750 [inline]
#0: ffff88807721c130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x32/0xd00 net/packet/af_packet.c:3263
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Tainted: G W 6.1.122-syzkaller #0
RIP: 0010:hlist_del include/linux/list.h:900 [inline]
RIP: 0010:__alloc_object lib/debugobjects.c:214 [inline]
RIP: 0010:alloc_object+0x160/0x6c0 lib/debugobjects.c:227
Code: 49 be 00 00 00 00 00 fc ff df 43 80 3c 34 00 48 8b 1c 24 74 08 48 89 df e8 dd de 98 fd 48 bd 00 01 00 00 00 00 ad de 48 89 2b <43> 80 3c 37 00 74 08 4c 89 ef e8 c1 de 98 fd 48 83 c5 22 49 89 6d
RSP: 0018:ffffc90000107958 EFLAGS: 00000046
RAX: 1ffff1102981840f RBX: ffff88814c0c6f50 RCX: dffffc0000000000
RDX: ffffffff8b0dda80 RSI: ffffffff8b5e67a0 RDI: ffffffff8b5e6760
RBP: dead000000000100 R08: dffffc0000000000 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: 1ffff11029818dea
R13: ffff88814c0c6f58 R14: dffffc0000000000 R15: 1ffff11029818deb
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f64e177680 CR3: 000000000d08e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
lookup_object_or_alloc lib/debugobjects.c:588 [inline]
__debug_object_init+0xe9/0x450 lib/debugobjects.c:623
init_timer_on_stack_key kernel/time/timer.c:805 [inline]
schedule_timeout+0x11c/0x300 kernel/time/timer.c:1963
toggle_allocation_gate+0x23b/0x480 mm/kfence/core.c:811
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
HEAD commit: 563edd786f0a Linux 6.1.122
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10d3eaf8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b70d05b26edc7515
dashboard link: https://syzkaller.appspot.com/bug?extid=4337a9544ad38c676780
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156b66df980000
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d3eaf8580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f111015ce9f/disk-563edd78.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/821c260b7642/vmlinux-563edd78.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9fba8f114c58/bzImage-563edd78.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/20b8946b3c25/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4337a9...@syzkaller.appspotmail.com
Tainted: G W 6.1.122-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor361 state:D stack:29336 pid:4266 ppid:4247 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__do_sys_mkdir fs/namei.c:4151 [inline]
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__se_sys_mkdir fs/namei.c:4149 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4149
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:0x7f92690ecd89
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RSP: 002b:00007f9269088228 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f926917e6b8 RCX: 00007f92690ecd89
RDX: 00007f92690c6316 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f926917e6b0 R08: 00007ffc82c71207 R09: 00007f92690886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f926917e6bc
R13: 0031656c69662f2e R14: 00007f9269141160 R15: 00007ffc82c71208
</TASK>
INFO: task syz-executor361:4265 blocked for more than 144 seconds.
Tainted: G W 6.1.122-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor361 state:D stack:29336 pid:4265 ppid:4249 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__do_sys_mkdir fs/namei.c:4151 [inline]
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__se_sys_mkdir fs/namei.c:4149 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4149
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:0x7f92690ecd89
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RSP: 002b:00007f9269088228 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f926917e6b8 RCX: 00007f92690ecd89
RDX: 00007f92690c6316 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f926917e6b0 R08: 00007ffc82c71207 R09: 00007f92690886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f926917e6bc
R13: 0031656c69662f2e R14: 00007f9269141160 R15: 00007ffc82c71208
</TASK>
INFO: task syz-executor361:4263 blocked for more than 145 seconds.
Tainted: G W 6.1.122-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor361 state:D stack:29336 pid:4263 ppid:4250 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__do_sys_mkdir fs/namei.c:4151 [inline]
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__se_sys_mkdir fs/namei.c:4149 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4149
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:0x7f92690ecd89
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RSP: 002b:00007f9269088228 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f926917e6b8 RCX: 00007f92690ecd89
RDX: 00007f92690c6316 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f926917e6b0 R08: 00007ffc82c71207 R09: 00007f92690886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f926917e6bc
R13: 0031656c69662f2e R14: 00007f9269141160 R15: 00007ffc82c71208
</TASK>
INFO: task syz-executor361:4264 blocked for more than 145 seconds.
Tainted: G W 6.1.122-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor361 state:D stack:28464 pid:4264 ppid:4251 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__do_sys_mkdir fs/namei.c:4151 [inline]
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__se_sys_mkdir fs/namei.c:4149 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4149
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:0x7f92690ecd89
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RSP: 002b:00007f9269088228 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f926917e6b8 RCX: 00007f92690ecd89
RDX: 00007f92690c6316 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f926917e6b0 R08: 00007ffc82c71207 R09: 00007f92690886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f926917e6bc
R13: 0031656c69662f2e R14: 00007f9269141160 R15: 00007ffc82c71208
</TASK>
INFO: task syz-executor361:4267 blocked for more than 146 seconds.
Tainted: G W 6.1.122-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor361 state:D stack:29336 pid:4267 ppid:4248 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__do_sys_mkdir fs/namei.c:4151 [inline]
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 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:3876
do_mkdirat+0xba/0x360 fs/namei.c:4121
__se_sys_mkdir fs/namei.c:4149 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4149
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:0x7f92690ecd89
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RSP: 002b:00007f9269088228 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f926917e6b8 RCX: 00007f92690ecd89
RDX: 00007f92690c6316 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f926917e6b0 R08: 00007ffc82c71207 R09: 00007f92690886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f926917e6bc
R13: 0031656c69662f2e R14: 00007f9269141160 R15: 00007ffc82c71208
</TASK>
Showing all locks held in the system:
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d32b290 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x34/0xde0 kernel/rcu/tasks.h:543
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d32bab0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x34/0xde0 kernel/rcu/tasks.h:543
2 locks held by kworker/1:0/22:
#0: ffff888017c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc900001c7d20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
1 lock held by khungtaskd/27:
#0: ffffffff8d32b0c0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8d32b0c0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8d32b0c0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6510
1 lock held by kswapd0/83:
2 locks held by getty/4012:
#0: ffff888030d4b098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000325e2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2198
3 locks held by syz-executor361/4259:
2 locks held by syz-executor361/4266:
#0: ffff888079844460 (sb_writers#10){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88806e0886d0 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff88806e0886d0 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
2 locks held by syz-executor361/4260:
2 locks held by syz-executor361/4265:
#0: ffff8880302f2460 (sb_writers#10){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88806e0586d0 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff88806e0586d0 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
2 locks held by syz-executor361/4257:
2 locks held by syz-executor361/4263:
#0: ffff888030e78460 (sb_writers#10){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88806e088188 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff88806e088188 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
3 locks held by syz-executor361/4262:
2 locks held by syz-executor361/4264:
#0: ffff8880736dc460 (sb_writers#10){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88806e088c18 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff88806e088c18 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
5 locks held by syz-executor361/4258:
2 locks held by syz-executor361/4267:
#0: ffff888029cf4460 (sb_writers#10){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
#1: ffff88806e058188 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
#1: ffff88806e058188 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3876
2 locks held by dhcpcd/4292:
#0: ffff8880244f8130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1750 [inline]
#0: ffff8880244f8130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x32/0xd00 net/packet/af_packet.c:3263
#1: ffffffff8d3306f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#1: ffffffff8d3306f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x360/0x930 kernel/rcu/tree_exp.h:962
1 lock held by dhcpcd/4293:
#0: ffff88807721c130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1750 [inline]
#0: ffff88807721c130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x32/0xd00 net/packet/af_packet.c:3263
=============================================
NMI backtrace for cpu 0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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+0x1ae/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:295
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 11 Comm: kworker/u4:1 Tainted: G W 6.1.122-syzkaller #0
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+0x1ae/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:295
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:hlist_del include/linux/list.h:900 [inline]
RIP: 0010:__alloc_object lib/debugobjects.c:214 [inline]
RIP: 0010:alloc_object+0x160/0x6c0 lib/debugobjects.c:227
Code: 49 be 00 00 00 00 00 fc ff df 43 80 3c 34 00 48 8b 1c 24 74 08 48 89 df e8 dd de 98 fd 48 bd 00 01 00 00 00 00 ad de 48 89 2b <43> 80 3c 37 00 74 08 4c 89 ef e8 c1 de 98 fd 48 83 c5 22 49 89 6d
RSP: 0018:ffffc90000107958 EFLAGS: 00000046
RAX: 1ffff1102981840f RBX: ffff88814c0c6f50 RCX: dffffc0000000000
RDX: ffffffff8b0dda80 RSI: ffffffff8b5e67a0 RDI: ffffffff8b5e6760
RBP: dead000000000100 R08: dffffc0000000000 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: 1ffff11029818dea
R13: ffff88814c0c6f58 R14: dffffc0000000000 R15: 1ffff11029818deb
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f64e177680 CR3: 000000000d08e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
lookup_object_or_alloc lib/debugobjects.c:588 [inline]
__debug_object_init+0xe9/0x450 lib/debugobjects.c:623
init_timer_on_stack_key kernel/time/timer.c:805 [inline]
schedule_timeout+0x11c/0x300 kernel/time/timer.c:1963
toggle_allocation_gate+0x23b/0x480 mm/kfence/core.c:811
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:295
</TASK>
---
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
Reply all
Reply to author
Forward
0 new messages