[v5.15] INFO: task hung in lock_rename
4 views
Skip to first unread message
syzbot
Mar 30, 2023, 2:48:49 PM3/30/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: c957cbb87315 Linux 5.15.105
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11060185c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f83fab0469f5de7
dashboard link: https://syzkaller.appspot.com/bug?extid=e97ae9118283c41cf24a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/35817fda76e5/disk-c957cbb8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/80f96399b8d4/vmlinux-c957cbb8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4336a6ad59ec/bzImage-c957cbb8.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e97ae9...@syzkaller.appspotmail.com
INFO: task syz-executor.5:11185 blocked for more than 143 seconds.
Not tainted 5.15.105-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:26912 pid:11185 ppid: 3624 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
rwsem_down_write_slowpath+0xebb/0x15c0 kernel/locking/rwsem.c:1157
__down_write_common kernel/locking/rwsem.c:1284 [inline]
__down_write kernel/locking/rwsem.c:1293 [inline]
down_write_nested+0x16d/0x180 kernel/locking/rwsem.c:1658
lock_rename+0x182/0x1a0
do_renameat2+0x545/0x13b0 fs/namei.c:4828
__do_sys_renameat2 fs/namei.c:4920 [inline]
__se_sys_renameat2 fs/namei.c:4917 [inline]
__x64_sys_renameat2+0xce/0xe0 fs/namei.c:4917
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8a38c4e0f9
RSP: 002b:00007f8a3719f168 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007f8a38d6e050 RCX: 00007f8a38c4e0f9
RDX: 0000000000000004 RSI: 0000000020000180 RDI: 0000000000000004
RBP: 00007f8a38ca9b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000380 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc198337cf R14: 00007f8a3719f300 R15: 0000000000022000
</TASK>
INFO: task syz-executor.5:11188 blocked for more than 143 seconds.
Not tainted 5.15.105-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:26864 pid:11188 ppid: 3624 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
rwsem_down_write_slowpath+0xebb/0x15c0 kernel/locking/rwsem.c:1157
__down_write_common kernel/locking/rwsem.c:1284 [inline]
__down_write kernel/locking/rwsem.c:1293 [inline]
down_write_nested+0x16d/0x180 kernel/locking/rwsem.c:1658
inode_lock_nested include/linux/fs.h:822 [inline]
ext4_rename fs/ext4/namei.c:3835 [inline]
ext4_rename2+0x1031/0x42a0 fs/ext4/namei.c:4207
vfs_rename+0xd8f/0x1190 fs/namei.c:4736
do_renameat2+0xb97/0x13b0 fs/namei.c:4887
__do_sys_rename fs/namei.c:4933 [inline]
__se_sys_rename fs/namei.c:4931 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:4931
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8a38c4e0f9
RSP: 002b:00007f8a3717e168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f8a38d6e120 RCX: 00007f8a38c4e0f9
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000020000200
RBP: 00007f8a38ca9b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc198337cf R14: 00007f8a3717e300 R15: 0000000000022000
</TASK>
INFO: task syz-executor.5:11195 blocked for more than 144 seconds.
Not tainted 5.15.105-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:27872 pid:11195 ppid: 3624 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
rwsem_down_write_slowpath+0xebb/0x15c0 kernel/locking/rwsem.c:1157
__down_write_common kernel/locking/rwsem.c:1284 [inline]
__down_write kernel/locking/rwsem.c:1293 [inline]
down_write+0x164/0x170 kernel/locking/rwsem.c:1542
inode_lock include/linux/fs.h:787 [inline]
open_last_lookups fs/namei.c:3459 [inline]
path_openat+0x824/0x2f20 fs/namei.c:3669
do_filp_open+0x21c/0x460 fs/namei.c:3699
do_sys_openat2+0x13b/0x500 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_creat fs/open.c:1301 [inline]
__se_sys_creat fs/open.c:1295 [inline]
__x64_sys_creat+0x11f/0x160 fs/open.c:1295
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8a38c4e0f9
RSP: 002b:00007f8a3715d168 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f8a38d6e1f0 RCX: 00007f8a38c4e0f9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000140
RBP: 00007f8a38ca9b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc198337cf R14: 00007f8a3715d300 R15: 0000000000022000
</TASK>
Showing all locks held in the system:
2 locks held by ksoftirqd/1/20:
1 lock held by khungtaskd/27:
#0: ffffffff8c91b920 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3270:
#0: ffff888024ae8098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bb32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
2 locks held by syz-fuzzer/3585:
#0: ffff888030bfa5f0 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x261/0x300 fs/file.c:1073
#1: ffff88802ffd03f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: iterate_dir+0x10a/0x570 fs/readdir.c:55
2 locks held by kworker/u4:6/3742:
2 locks held by kworker/1:0/10709:
#0: ffff888011c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc90003d3fd20 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
4 locks held by syz-executor.5/11185:
#0: ffff88807f0f8460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
#1: ffff88807f0f8748 (&type->s_vfs_rename_key){+.+.}-{3:3}, at: lock_rename+0x54/0x1a0 fs/namei.c:2971
#2: ffff88803604bfc0 (&type->i_mutex_dir_key#4/1){+.+.}-{3:3}, at: lock_rename+0x13a/0x1a0
#3: ffff88802fd483f0 (&type->i_mutex_dir_key#4/5){+.+.}-{3:3}, at: lock_rename+0x182/0x1a0
4 locks held by syz-executor.5/11188:
#0: ffff88807f0f8460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
#1: ffff88802ffd03f0 (&type->i_mutex_dir_key#4/1){+.+.}-{3:3}, at: lock_rename+0x182/0x1a0
#2: ffff88802fd483f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#2: ffff88802fd483f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: vfs_rename+0x78f/0x1190 fs/namei.c:4708
#3: ffff88803604bfc0 (&type->i_mutex_dir_key#4/4){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline]
#3: ffff88803604bfc0 (&type->i_mutex_dir_key#4/4){+.+.}-{3:3}, at: ext4_rename fs/ext4/namei.c:3835 [inline]
#3: ffff88803604bfc0 (&type->i_mutex_dir_key#4/4){+.+.}-{3:3}, at: ext4_rename2+0x1031/0x42a0 fs/ext4/namei.c:4207
2 locks held by syz-executor.5/11195:
#0: ffff88807f0f8460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
#1: ffff88802fd483f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88802fd483f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: open_last_lookups fs/namei.c:3459 [inline]
#1: ffff88802fd483f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: path_openat+0x824/0x2f20 fs/namei.c:3669
2 locks held by dhcpcd/11261:
#0: ffff888086b42120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1649 [inline]
#0: ffff888086b42120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x2a/0xc90 net/packet/af_packet.c:3159
#1: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#1: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x280/0x740 kernel/rcu/tree_exp.h:840
2 locks held by dhcpcd/11262:
#0: ffff888086bbc120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1649 [inline]
#0: ffff888086bbc120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x2a/0xc90 net/packet/af_packet.c:3159
#1: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#1: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x350/0x740 kernel/rcu/tree_exp.h:840
1 lock held by dhcpcd/11263:
#0: ffff888086a26120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1649 [inline]
#0: ffff888086a26120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x2a/0xc90 net/packet/af_packet.c:3159
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.105-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted 5.15.105-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:memset_erms+0xb/0x10 arch/x86/lib/memset_64.S:65
Code: 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 f3 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3 aa <4c> 89 c8 c3 90 49 89 fa 40 0f b6 ce 48 b8 01 01 01 01 01 01 01 01
RSP: 0018:ffffc90000da6a00 EFLAGS: 00000202
RAX: 0000000000000000 RBX: ffffc90000da6b10 RCX: 0000000000000000
RDX: 0000000000000010 RSI: 0000000000000000 RDI: ffffc90000da6b20
RBP: ffffffff8e594d28 R08: dffffc0000000000 R09: ffffc90000da6b10
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffffffff1cb29a5
R13: 1ffffffff1cb29a5 R14: ffffffff8e594d24 R15: ffffc90000da6ac0
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056278038d680 CR3: 0000000078f97000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
unwind_next_frame+0xbc8/0x1fa0 arch/x86/kernel/unwind_orc.c:547
arch_stack_walk+0x10d/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:46 [inline]
set_alloc_info mm/kasan/common.c:434 [inline]
__kasan_slab_alloc+0x8e/0xc0 mm/kasan/common.c:467
kasan_slab_alloc include/linux/kasan.h:254 [inline]
slab_post_alloc_hook+0x53/0x380 mm/slab.h:519
slab_alloc_node mm/slub.c:3220 [inline]
kmem_cache_alloc_node+0x121/0x2c0 mm/slub.c:3256
__alloc_skb+0xdd/0x590 net/core/skbuff.c:415
alloc_skb include/linux/skbuff.h:1166 [inline]
nlmsg_new include/net/netlink.h:953 [inline]
fdb_notify+0xa3/0x160 net/bridge/br_fdb.c:800
br_fdb_update+0x508/0x670 net/bridge/br_fdb.c:624
br_handle_frame_finish+0x508/0x1700 net/bridge/br_input.c:103
br_nf_hook_thresh+0x46a/0x580 net/bridge/br_netfilter_hooks.c:1042
br_nf_pre_routing_finish_ipv6+0xa08/0xcd0
NF_HOOK include/linux/netfilter.h:307 [inline]
br_nf_pre_routing_ipv6+0x35d/0x720 net/bridge/br_netfilter_ipv6.c:237
nf_hook_entry_hookfn include/linux/netfilter.h:142 [inline]
nf_hook_bridge_pre net/bridge/br_input.c:237 [inline]
br_handle_frame+0x8a8/0x10b0 net/bridge/br_input.c:377
__netif_receive_skb_core+0x13b9/0x3df0 net/core/dev.c:5352
__netif_receive_skb_one_core net/core/dev.c:5456 [inline]
__netif_receive_skb+0x11c/0x530 net/core/dev.c:5572
process_backlog+0x363/0x7f0 net/core/dev.c:6449
__napi_poll+0xc7/0x440 net/core/dev.c:7008
napi_poll net/core/dev.c:7075 [inline]
net_rx_action+0x617/0xda0 net/core/dev.c:7162
__do_softirq+0x3b3/0x93a kernel/softirq.c:558
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:920
smpboot_thread_fn+0x51b/0x9d0 kernel/smpboot.c:164
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
---
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.
syzbot found the following issue on:
HEAD commit: c957cbb87315 Linux 5.15.105
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11060185c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f83fab0469f5de7
dashboard link: https://syzkaller.appspot.com/bug?extid=e97ae9118283c41cf24a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/35817fda76e5/disk-c957cbb8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/80f96399b8d4/vmlinux-c957cbb8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4336a6ad59ec/bzImage-c957cbb8.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e97ae9...@syzkaller.appspotmail.com
INFO: task syz-executor.5:11185 blocked for more than 143 seconds.
Not tainted 5.15.105-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:26912 pid:11185 ppid: 3624 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
rwsem_down_write_slowpath+0xebb/0x15c0 kernel/locking/rwsem.c:1157
__down_write_common kernel/locking/rwsem.c:1284 [inline]
__down_write kernel/locking/rwsem.c:1293 [inline]
down_write_nested+0x16d/0x180 kernel/locking/rwsem.c:1658
lock_rename+0x182/0x1a0
do_renameat2+0x545/0x13b0 fs/namei.c:4828
__do_sys_renameat2 fs/namei.c:4920 [inline]
__se_sys_renameat2 fs/namei.c:4917 [inline]
__x64_sys_renameat2+0xce/0xe0 fs/namei.c:4917
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8a38c4e0f9
RSP: 002b:00007f8a3719f168 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007f8a38d6e050 RCX: 00007f8a38c4e0f9
RDX: 0000000000000004 RSI: 0000000020000180 RDI: 0000000000000004
RBP: 00007f8a38ca9b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000380 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc198337cf R14: 00007f8a3719f300 R15: 0000000000022000
</TASK>
INFO: task syz-executor.5:11188 blocked for more than 143 seconds.
Not tainted 5.15.105-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:26864 pid:11188 ppid: 3624 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
rwsem_down_write_slowpath+0xebb/0x15c0 kernel/locking/rwsem.c:1157
__down_write_common kernel/locking/rwsem.c:1284 [inline]
__down_write kernel/locking/rwsem.c:1293 [inline]
down_write_nested+0x16d/0x180 kernel/locking/rwsem.c:1658
inode_lock_nested include/linux/fs.h:822 [inline]
ext4_rename fs/ext4/namei.c:3835 [inline]
ext4_rename2+0x1031/0x42a0 fs/ext4/namei.c:4207
vfs_rename+0xd8f/0x1190 fs/namei.c:4736
do_renameat2+0xb97/0x13b0 fs/namei.c:4887
__do_sys_rename fs/namei.c:4933 [inline]
__se_sys_rename fs/namei.c:4931 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:4931
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8a38c4e0f9
RSP: 002b:00007f8a3717e168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f8a38d6e120 RCX: 00007f8a38c4e0f9
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000020000200
RBP: 00007f8a38ca9b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc198337cf R14: 00007f8a3717e300 R15: 0000000000022000
</TASK>
INFO: task syz-executor.5:11195 blocked for more than 144 seconds.
Not tainted 5.15.105-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:27872 pid:11195 ppid: 3624 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
rwsem_down_write_slowpath+0xebb/0x15c0 kernel/locking/rwsem.c:1157
__down_write_common kernel/locking/rwsem.c:1284 [inline]
__down_write kernel/locking/rwsem.c:1293 [inline]
down_write+0x164/0x170 kernel/locking/rwsem.c:1542
inode_lock include/linux/fs.h:787 [inline]
open_last_lookups fs/namei.c:3459 [inline]
path_openat+0x824/0x2f20 fs/namei.c:3669
do_filp_open+0x21c/0x460 fs/namei.c:3699
do_sys_openat2+0x13b/0x500 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_creat fs/open.c:1301 [inline]
__se_sys_creat fs/open.c:1295 [inline]
__x64_sys_creat+0x11f/0x160 fs/open.c:1295
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8a38c4e0f9
RSP: 002b:00007f8a3715d168 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f8a38d6e1f0 RCX: 00007f8a38c4e0f9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000140
RBP: 00007f8a38ca9b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc198337cf R14: 00007f8a3715d300 R15: 0000000000022000
</TASK>
Showing all locks held in the system:
2 locks held by ksoftirqd/1/20:
1 lock held by khungtaskd/27:
#0: ffffffff8c91b920 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3270:
#0: ffff888024ae8098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bb32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
2 locks held by syz-fuzzer/3585:
#0: ffff888030bfa5f0 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x261/0x300 fs/file.c:1073
#1: ffff88802ffd03f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: iterate_dir+0x10a/0x570 fs/readdir.c:55
2 locks held by kworker/u4:6/3742:
2 locks held by kworker/1:0/10709:
#0: ffff888011c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279
#1: ffffc90003d3fd20 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281
4 locks held by syz-executor.5/11185:
#0: ffff88807f0f8460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
#1: ffff88807f0f8748 (&type->s_vfs_rename_key){+.+.}-{3:3}, at: lock_rename+0x54/0x1a0 fs/namei.c:2971
#2: ffff88803604bfc0 (&type->i_mutex_dir_key#4/1){+.+.}-{3:3}, at: lock_rename+0x13a/0x1a0
#3: ffff88802fd483f0 (&type->i_mutex_dir_key#4/5){+.+.}-{3:3}, at: lock_rename+0x182/0x1a0
4 locks held by syz-executor.5/11188:
#0: ffff88807f0f8460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
#1: ffff88802ffd03f0 (&type->i_mutex_dir_key#4/1){+.+.}-{3:3}, at: lock_rename+0x182/0x1a0
#2: ffff88802fd483f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#2: ffff88802fd483f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: vfs_rename+0x78f/0x1190 fs/namei.c:4708
#3: ffff88803604bfc0 (&type->i_mutex_dir_key#4/4){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline]
#3: ffff88803604bfc0 (&type->i_mutex_dir_key#4/4){+.+.}-{3:3}, at: ext4_rename fs/ext4/namei.c:3835 [inline]
#3: ffff88803604bfc0 (&type->i_mutex_dir_key#4/4){+.+.}-{3:3}, at: ext4_rename2+0x1031/0x42a0 fs/ext4/namei.c:4207
2 locks held by syz-executor.5/11195:
#0: ffff88807f0f8460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
#1: ffff88802fd483f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88802fd483f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: open_last_lookups fs/namei.c:3459 [inline]
#1: ffff88802fd483f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: path_openat+0x824/0x2f20 fs/namei.c:3669
2 locks held by dhcpcd/11261:
#0: ffff888086b42120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1649 [inline]
#0: ffff888086b42120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x2a/0xc90 net/packet/af_packet.c:3159
#1: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#1: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x280/0x740 kernel/rcu/tree_exp.h:840
2 locks held by dhcpcd/11262:
#0: ffff888086bbc120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1649 [inline]
#0: ffff888086bbc120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x2a/0xc90 net/packet/af_packet.c:3159
#1: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#1: ffffffff8c91fe68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x350/0x740 kernel/rcu/tree_exp.h:840
1 lock held by dhcpcd/11263:
#0: ffff888086a26120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1649 [inline]
#0: ffff888086a26120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x2a/0xc90 net/packet/af_packet.c:3159
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.105-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted 5.15.105-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:memset_erms+0xb/0x10 arch/x86/lib/memset_64.S:65
Code: 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 f3 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3 aa <4c> 89 c8 c3 90 49 89 fa 40 0f b6 ce 48 b8 01 01 01 01 01 01 01 01
RSP: 0018:ffffc90000da6a00 EFLAGS: 00000202
RAX: 0000000000000000 RBX: ffffc90000da6b10 RCX: 0000000000000000
RDX: 0000000000000010 RSI: 0000000000000000 RDI: ffffc90000da6b20
RBP: ffffffff8e594d28 R08: dffffc0000000000 R09: ffffc90000da6b10
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffffffff1cb29a5
R13: 1ffffffff1cb29a5 R14: ffffffff8e594d24 R15: ffffc90000da6ac0
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056278038d680 CR3: 0000000078f97000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
unwind_next_frame+0xbc8/0x1fa0 arch/x86/kernel/unwind_orc.c:547
arch_stack_walk+0x10d/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:46 [inline]
set_alloc_info mm/kasan/common.c:434 [inline]
__kasan_slab_alloc+0x8e/0xc0 mm/kasan/common.c:467
kasan_slab_alloc include/linux/kasan.h:254 [inline]
slab_post_alloc_hook+0x53/0x380 mm/slab.h:519
slab_alloc_node mm/slub.c:3220 [inline]
kmem_cache_alloc_node+0x121/0x2c0 mm/slub.c:3256
__alloc_skb+0xdd/0x590 net/core/skbuff.c:415
alloc_skb include/linux/skbuff.h:1166 [inline]
nlmsg_new include/net/netlink.h:953 [inline]
fdb_notify+0xa3/0x160 net/bridge/br_fdb.c:800
br_fdb_update+0x508/0x670 net/bridge/br_fdb.c:624
br_handle_frame_finish+0x508/0x1700 net/bridge/br_input.c:103
br_nf_hook_thresh+0x46a/0x580 net/bridge/br_netfilter_hooks.c:1042
br_nf_pre_routing_finish_ipv6+0xa08/0xcd0
NF_HOOK include/linux/netfilter.h:307 [inline]
br_nf_pre_routing_ipv6+0x35d/0x720 net/bridge/br_netfilter_ipv6.c:237
nf_hook_entry_hookfn include/linux/netfilter.h:142 [inline]
nf_hook_bridge_pre net/bridge/br_input.c:237 [inline]
br_handle_frame+0x8a8/0x10b0 net/bridge/br_input.c:377
__netif_receive_skb_core+0x13b9/0x3df0 net/core/dev.c:5352
__netif_receive_skb_one_core net/core/dev.c:5456 [inline]
__netif_receive_skb+0x11c/0x530 net/core/dev.c:5572
process_backlog+0x363/0x7f0 net/core/dev.c:6449
__napi_poll+0xc7/0x440 net/core/dev.c:7008
napi_poll net/core/dev.c:7075 [inline]
net_rx_action+0x617/0xda0 net/core/dev.c:7162
__do_softirq+0x3b3/0x93a kernel/softirq.c:558
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:920
smpboot_thread_fn+0x51b/0x9d0 kernel/smpboot.c:164
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
---
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.
syzbot
Aug 23, 2023, 5:02:50 AM8/23/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages