[v6.1] INFO: task hung in tls_sk_proto_close
0 views
Skip to first unread message
syzbot
Sep 23, 2023, 5:40:42 PM9/23/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d23900f974e0 Linux 6.1.55
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1714bf6c680000
kernel config: https://syzkaller.appspot.com/x/.config?x=5bcd925baa8f3696
dashboard link: https://syzkaller.appspot.com/bug?extid=3b820d9fad6d470e1967
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/bdd6d6e750b0/disk-d23900f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a43703f89e81/vmlinux-d23900f9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/30f239dbfd4c/bzImage-d23900f9.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3b820d...@syzkaller.appspotmail.com
INFO: task syz-executor.4:3997 blocked for more than 143 seconds.
Not tainted 6.1.55-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:25000 pid:3997 ppid:3596 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
schedule_timeout+0xac/0x300 kernel/time/timer.c:1911
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x350/0x610 kernel/sched/completion.c:138
__flush_work+0x95b/0xad0 kernel/workqueue.c:3076
__cancel_work_timer+0x519/0x6a0 kernel/workqueue.c:3163
tls_sk_proto_close+0x121/0x980 net/tls/tls_main.c:327
inet_release+0x174/0x1f0 net/ipv4/af_inet.c:429
__sock_release net/socket.c:652 [inline]
sock_close+0xcd/0x230 net/socket.c:1370
__fput+0x3b7/0x890 fs/file_table.c:320
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xd9/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f604767b9da
RSP: 002b:00007fff0c9f3730 EFLAGS: 00000293
ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00007f604767b9da
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00007f604779d980 R08: 0000001b34020000 R09: 0000000000000262
R10: 00000000815ba1a7 R11: 0000000000000293 R12: 00000000001752a5
R13: ffffffffffffffff R14: 00007f6047200000 R15: 0000000000174f64
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d12a170 (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: ffffffff8d12a970 (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: ffffffff8d129fa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:306 [inline]
#0: ffffffff8d129fa0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:747 [inline]
#0: ffffffff8d129fa0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6493
2 locks held by getty/3307:
#0: ffff88814ba58098 (&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
3 locks held by kworker/1:4/21242:
#0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90014f2fd20 ((work_completion)(&(&sw_ctx_tx->tx_work.work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff88809057c4d8 (&ctx->tx_lock){+.+.}-{3:3}, at: tx_work_handler+0x107/0x200 net/tls/tls_sw.c:2430
3 locks held by kworker/1:13/21253:
#0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90015077d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffffffff8d12f578 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
#2: ffffffff8d12f578 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3b0/0x8a0 kernel/rcu/tree_exp.h:950
2 locks held by kworker/u4:15/30692:
2 locks held by kworker/1:8/726:
#0: ffff888012472538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc9000abe7d20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
1 lock held by syz-executor.4/3997:
#0: ffff8880703ad010 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
#0: ffff8880703ad010 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release net/socket.c:651 [inline]
#0: ffff8880703ad010 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: sock_close+0x98/0x230 net/socket.c:1370
1 lock held by syz-executor.4/6061:
#0: ffffffff8d12f440 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x48/0x5f0 kernel/rcu/tree.c:3965
1 lock held by syz-executor.3/6068:
#0: ffff8880767cc0e0 (&type->s_umount_key#94/1){+.+.}-{3:3}, at: alloc_super+0x217/0x930 fs/super.c:228
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.1.55-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/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+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:306
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4068 Comm: syz-executor.4 Not tainted 6.1.55-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
RIP: 0010:PageTail include/linux/page-flags.h:292 [inline]
RIP: 0010:folio_flags include/linux/page-flags.h:319 [inline]
RIP: 0010:folio_test_unevictable include/linux/page-flags.h:558 [inline]
RIP: 0010:folio_inc_refs mm/swap.c:436 [inline]
RIP: 0010:folio_mark_accessed+0xeb/0x1c90 mm/swap.c:478
Code: 60 48 8b 44 24 10 4c 8d 78 08 4d 89 fe 49 c1 ee 03 48 b8 00 00 00 00 00 fc ff df 41 80 3c 06 00 74 08 4c 89 ff e8 95 bb 25 00 <49> 8b 1f 48 89 de 48 83 e6 01 31 ff e8 64 9c ce ff 48 83 e3 01 0f
RSP: 0018:ffffc9000b7af560 EFLAGS: 00000246
RAX: dffffc0000000000 RBX: 00fff3800000205a RCX: 1ffff920016f5eb8
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffea000188cd80
RBP: ffffc9000b7af630 R08: ffffffff81bacb04 R09: fffffbfff1ce7596
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffffd40003119b0
R13: ffff8880700a7ae0 R14: 1ffffd40003119b1 R15: ffffea000188cd88
FS: 00005555571ad480(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3defb04497 CR3: 000000007b678000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
__find_get_block+0x2c8/0x1120 fs/buffer.c:1311
__getblk_gfp+0x2d/0xa20 fs/buffer.c:1329
sb_getblk include/linux/buffer_head.h:356 [inline]
__ext4_get_inode_loc+0x4ed/0xe40 fs/ext4/inode.c:4488
ext4_get_inode_loc fs/ext4/inode.c:4616 [inline]
ext4_reserve_inode_write+0x17e/0x360 fs/ext4/inode.c:5846
__ext4_mark_inode_dirty+0x1f2/0x920 fs/ext4/inode.c:6023
ext4_evict_inode+0xd0b/0x1150 fs/ext4/inode.c:327
evict+0x2a4/0x620 fs/inode.c:664
do_unlinkat+0x502/0x940 fs/namei.c:4327
__do_sys_unlink fs/namei.c:4368 [inline]
__se_sys_unlink fs/namei.c:4366 [inline]
__x64_sys_unlink+0x45/0x50 fs/namei.c:4366
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+0x63/0xcd
RIP: 0033:0x7fcb1307c297
Code: 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 57 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd390158f8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcb1307c297
RDX: 00007ffd39015920 RSI: 00007ffd390159b0 RDI: 00007ffd390159b0
RBP: 00007ffd390159b0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000100 R11: 0000000000000206 R12: 00007ffd39016a70
R13: 00007fcb130c73b9 R14: 000000000019cd88 R15: 000000000000000e
</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.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, 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: d23900f974e0 Linux 6.1.55
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1714bf6c680000
kernel config: https://syzkaller.appspot.com/x/.config?x=5bcd925baa8f3696
dashboard link: https://syzkaller.appspot.com/bug?extid=3b820d9fad6d470e1967
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/bdd6d6e750b0/disk-d23900f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a43703f89e81/vmlinux-d23900f9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/30f239dbfd4c/bzImage-d23900f9.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3b820d...@syzkaller.appspotmail.com
INFO: task syz-executor.4:3997 blocked for more than 143 seconds.
Not tainted 6.1.55-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:25000 pid:3997 ppid:3596 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
schedule_timeout+0xac/0x300 kernel/time/timer.c:1911
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x350/0x610 kernel/sched/completion.c:138
__flush_work+0x95b/0xad0 kernel/workqueue.c:3076
__cancel_work_timer+0x519/0x6a0 kernel/workqueue.c:3163
tls_sk_proto_close+0x121/0x980 net/tls/tls_main.c:327
inet_release+0x174/0x1f0 net/ipv4/af_inet.c:429
__sock_release net/socket.c:652 [inline]
sock_close+0xcd/0x230 net/socket.c:1370
__fput+0x3b7/0x890 fs/file_table.c:320
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xd9/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f604767b9da
RSP: 002b:00007fff0c9f3730 EFLAGS: 00000293
ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00007f604767b9da
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00007f604779d980 R08: 0000001b34020000 R09: 0000000000000262
R10: 00000000815ba1a7 R11: 0000000000000293 R12: 00000000001752a5
R13: ffffffffffffffff R14: 00007f6047200000 R15: 0000000000174f64
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d12a170 (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: ffffffff8d12a970 (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: ffffffff8d129fa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:306 [inline]
#0: ffffffff8d129fa0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:747 [inline]
#0: ffffffff8d129fa0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6493
2 locks held by getty/3307:
#0: ffff88814ba58098 (&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
3 locks held by kworker/1:4/21242:
#0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90014f2fd20 ((work_completion)(&(&sw_ctx_tx->tx_work.work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff88809057c4d8 (&ctx->tx_lock){+.+.}-{3:3}, at: tx_work_handler+0x107/0x200 net/tls/tls_sw.c:2430
3 locks held by kworker/1:13/21253:
#0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90015077d20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffffffff8d12f578 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
#2: ffffffff8d12f578 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3b0/0x8a0 kernel/rcu/tree_exp.h:950
2 locks held by kworker/u4:15/30692:
2 locks held by kworker/1:8/726:
#0: ffff888012472538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc9000abe7d20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
1 lock held by syz-executor.4/3997:
#0: ffff8880703ad010 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
#0: ffff8880703ad010 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release net/socket.c:651 [inline]
#0: ffff8880703ad010 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: sock_close+0x98/0x230 net/socket.c:1370
1 lock held by syz-executor.4/6061:
#0: ffffffff8d12f440 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x48/0x5f0 kernel/rcu/tree.c:3965
1 lock held by syz-executor.3/6068:
#0: ffff8880767cc0e0 (&type->s_umount_key#94/1){+.+.}-{3:3}, at: alloc_super+0x217/0x930 fs/super.c:228
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.1.55-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/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+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:306
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4068 Comm: syz-executor.4 Not tainted 6.1.55-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
RIP: 0010:PageTail include/linux/page-flags.h:292 [inline]
RIP: 0010:folio_flags include/linux/page-flags.h:319 [inline]
RIP: 0010:folio_test_unevictable include/linux/page-flags.h:558 [inline]
RIP: 0010:folio_inc_refs mm/swap.c:436 [inline]
RIP: 0010:folio_mark_accessed+0xeb/0x1c90 mm/swap.c:478
Code: 60 48 8b 44 24 10 4c 8d 78 08 4d 89 fe 49 c1 ee 03 48 b8 00 00 00 00 00 fc ff df 41 80 3c 06 00 74 08 4c 89 ff e8 95 bb 25 00 <49> 8b 1f 48 89 de 48 83 e6 01 31 ff e8 64 9c ce ff 48 83 e3 01 0f
RSP: 0018:ffffc9000b7af560 EFLAGS: 00000246
RAX: dffffc0000000000 RBX: 00fff3800000205a RCX: 1ffff920016f5eb8
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffea000188cd80
RBP: ffffc9000b7af630 R08: ffffffff81bacb04 R09: fffffbfff1ce7596
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffffd40003119b0
R13: ffff8880700a7ae0 R14: 1ffffd40003119b1 R15: ffffea000188cd88
FS: 00005555571ad480(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3defb04497 CR3: 000000007b678000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
__find_get_block+0x2c8/0x1120 fs/buffer.c:1311
__getblk_gfp+0x2d/0xa20 fs/buffer.c:1329
sb_getblk include/linux/buffer_head.h:356 [inline]
__ext4_get_inode_loc+0x4ed/0xe40 fs/ext4/inode.c:4488
ext4_get_inode_loc fs/ext4/inode.c:4616 [inline]
ext4_reserve_inode_write+0x17e/0x360 fs/ext4/inode.c:5846
__ext4_mark_inode_dirty+0x1f2/0x920 fs/ext4/inode.c:6023
ext4_evict_inode+0xd0b/0x1150 fs/ext4/inode.c:327
evict+0x2a4/0x620 fs/inode.c:664
do_unlinkat+0x502/0x940 fs/namei.c:4327
__do_sys_unlink fs/namei.c:4368 [inline]
__se_sys_unlink fs/namei.c:4366 [inline]
__x64_sys_unlink+0x45/0x50 fs/namei.c:4366
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+0x63/0xcd
RIP: 0033:0x7fcb1307c297
Code: 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 57 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd390158f8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcb1307c297
RDX: 00007ffd39015920 RSI: 00007ffd390159b0 RDI: 00007ffd390159b0
RBP: 00007ffd390159b0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000100 R11: 0000000000000206 R12: 00007ffd39016a70
R13: 00007fcb130c73b9 R14: 000000000019cd88 R15: 000000000000000e
</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.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Feb 18, 2024, 4:46:14 PMFeb 18
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