[v5.15] INFO: task hung in process_measurement
3 views
Skip to first unread message
syzbot
Jul 23, 2023, 5:34:53 AM7/23/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11b9f00ca80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f546a5c7ff981a94
dashboard link: https://syzkaller.appspot.com/bug?extid=97981def810b15648b73
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/601dfce79849/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b8e802138c25/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9b3b48ff5c05/bzImage-d54cfc42.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+97981d...@syzkaller.appspotmail.com
INFO: task syz-executor.4:18103 blocked for more than 143 seconds.
Not tainted 5.15.120-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:26192 pid:18103 ppid: 3557 flags:0x00004006
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]
process_measurement+0x435/0x1d60 security/integrity/ima/ima_main.c:241
ima_file_check+0xf3/0x180 security/integrity/ima/ima_main.c:519
do_open fs/namei.c:3540 [inline]
path_openat+0x2745/0x2f20 fs/namei.c:3672
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_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1238
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:0x7f3029ab4b29
RSP: 002b:00007f301fff40c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f3029bd4120 RCX: 00007f3029ab4b29
RDX: 0b00000000065808 RSI: 0000000020000080 RDI: ffffffffffffff9c
RBP: 00007f3029b0047a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f3029bd4120 R15: 00007fff7fa4a6c8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/26:
#0: ffffffff8c91e6a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3258:
#0: ffff88802488b098 (&tty->ldisc_sem
){++++}-{0:0}
, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900022a32e8 (
&ldata->atomic_read_lock
){+.+.}-{3:3}
, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
5 locks held by kworker/0:6/3634:
#0:
ffff8881421b9138
(
(wq_completion)usb_hub_wq
){+.+.}-{0:0}
, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc9000451fd20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
#2: ffff8881480cd220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#2: ffff8881480cd220 (&dev->mutex){....}-{3:3}, at: hub_event+0x207/0x56d0 drivers/usb/core/hub.c:5676
#3:
ffff8880b9a396d8
(
&rq->__lock
){-.-.}-{2:2}
, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
#4:
ffff8880b9a27848
(
&per_cpu_ptr(group->pcpu, cpu)->seq
){-.-.}-{0:0}, at: psi_task_switch+0x53d/0x810 kernel/sched/psi.c:891
4 locks held by kworker/1:14/3800:
#0: ffff888011c65538 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc90004fafd20 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
#2:
ffff888080c460e0
(
&type->s_umount_key#74){++++}-{3:3}, at: flush_old_commits+0xc7/0x2e0 fs/reiserfs/super.c:97
#3: ffff88803f843090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27
2 locks held by kworker/0:16/9373:
#0: ffff888011c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1:
ffffc900106bfd20
(
(work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
7 locks held by syz-executor.4/18069:
1 lock held by syz-executor.4/18103:
#0: ffff888081d5d900 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#0: ffff888081d5d900 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: process_measurement+0x435/0x1d60 security/integrity/ima/ima_main.c:241
1 lock held by syz-executor.5/21118:
#0: ffffffff8c943f50 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x285/0x2480 kernel/exit.c:828
1 lock held by syz-executor.5/21119:
#0: ffffffff8c943f50 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x285/0x2480 kernel/exit.c:828
1 lock held by syz-executor.1/21139:
#0: ffffffff8c922af0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x9c/0x4e0 kernel/rcu/tree.c:4018
1 lock held by syz-executor.2/21143:
#0: ffffffff8c943f50 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: copy_process+0x2210/0x3ef0 kernel/fork.c:2299
5 locks held by kvm-nx-lpage-re/21145:
#0: ffffffff8c943d68 (cgroup_mutex){+.+.}-{3:3}, at: cgroup_attach_task_all+0x23/0x150 kernel/cgroup/cgroup-v1.c:61
#1:
ffffffff8c7bc010
(cpu_hotplug_lock){++++}-{0:0}, at: cgroup_attach_task_all+0x28/0x150 kernel/cgroup/cgroup-v1.c:62
#2: ffffffff8c943f50 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: cgroup_attach_task_all+0x34/0x150 kernel/cgroup/cgroup-v1.c:63
#3: ffffffff8c950130 (&cpuset_rwsem){++++}-{0:0}, at: cpuset_can_attach+0x1e9/0x490 kernel/cgroup/cpuset.c:2197
#4:
ffffffff8c922be8
(
rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x280/0x740 kernel/rcu/tree_exp.h:842
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 26 Comm: khungtaskd Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/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 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 21159 Comm: syz-executor.1 Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
RIP: 0010:rb_next+0xa2/0xe0 lib/rbtree.c:517
Code: 48 c1 e8 03 42 80 3c 38 00 74 e3 48 89 df e8 e5 d1 9e fd eb d9 4c 3b 63 08 49 89 dc 75 3d 4c 89 e0 48 c1 e8 03 42 80 3c 38 00 <74> 08 4c 89 e7 e8 c4 d1 9e fd 49 8b 1c 24 48 83 e3 fc 0f 84 79 ff
RSP: 0018:ffffc9000a9e7770 EFLAGS: 00000046
RAX: 1ffff11002d31b42 RBX: 1ffff1100edd7009 RCX: dffffc0000000000
RDX: ffffc9000a9e79a0 RSI: ffff88801698da00 RDI: ffff88801698da10
RBP: ffff888076eb8000 R08: dffffc0000000000 R09: fffffbfff1bc7e0e
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801698da10
R13: ffff888076eb8048 R14: 0000000000000000 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3861f03d00 CR3: 000000001a664000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
rb_erase_cached include/linux/rbtree.h:124 [inline]
__dequeue_entity kernel/sched/fair.c:585 [inline]
set_next_entity+0x27b/0x580 kernel/sched/fair.c:4694
pick_next_task_fair+0x379/0x9c0 kernel/sched/fair.c:7586
__pick_next_task kernel/sched/core.c:5646 [inline]
pick_next_task kernel/sched/core.c:5754 [inline]
__schedule+0x86d/0x4590 kernel/sched/core.c:6336
do_task_dead+0xba/0xc0 kernel/sched/core.c:6390
do_exit+0x1b3e/0x2480 kernel/exit.c:923
do_group_exit+0x144/0x310 kernel/exit.c:994
get_signal+0xc66/0x14e0 kernel/signal.c:2889
arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:865
handle_signal_work kernel/entry/common.c:148 [inline]
exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:172
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f3863a48b29
Code: Unable to access opcode bytes at RIP 0x7f3863a48aff.
RSP: 002b:00007f3861f88178 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007f3863b68128 RCX: 00007f3863a48b29
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f3863b68128
RBP: 00007f3863b68120 R08: 00007f3861f886c0 R09: 00007f3861f886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f3863b6812c
R13: 000000000000006e R14: 00007ffe3df2d400 R15: 00007ffe3df2d4e8
</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 change 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: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11b9f00ca80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f546a5c7ff981a94
dashboard link: https://syzkaller.appspot.com/bug?extid=97981def810b15648b73
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/601dfce79849/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b8e802138c25/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9b3b48ff5c05/bzImage-d54cfc42.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+97981d...@syzkaller.appspotmail.com
INFO: task syz-executor.4:18103 blocked for more than 143 seconds.
Not tainted 5.15.120-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:26192 pid:18103 ppid: 3557 flags:0x00004006
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]
process_measurement+0x435/0x1d60 security/integrity/ima/ima_main.c:241
ima_file_check+0xf3/0x180 security/integrity/ima/ima_main.c:519
do_open fs/namei.c:3540 [inline]
path_openat+0x2745/0x2f20 fs/namei.c:3672
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_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1238
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:0x7f3029ab4b29
RSP: 002b:00007f301fff40c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f3029bd4120 RCX: 00007f3029ab4b29
RDX: 0b00000000065808 RSI: 0000000020000080 RDI: ffffffffffffff9c
RBP: 00007f3029b0047a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f3029bd4120 R15: 00007fff7fa4a6c8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/26:
#0: ffffffff8c91e6a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3258:
#0: ffff88802488b098 (&tty->ldisc_sem
){++++}-{0:0}
, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900022a32e8 (
&ldata->atomic_read_lock
){+.+.}-{3:3}
, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
5 locks held by kworker/0:6/3634:
#0:
ffff8881421b9138
(
(wq_completion)usb_hub_wq
){+.+.}-{0:0}
, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc9000451fd20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
#2: ffff8881480cd220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#2: ffff8881480cd220 (&dev->mutex){....}-{3:3}, at: hub_event+0x207/0x56d0 drivers/usb/core/hub.c:5676
#3:
ffff8880b9a396d8
(
&rq->__lock
){-.-.}-{2:2}
, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
#4:
ffff8880b9a27848
(
&per_cpu_ptr(group->pcpu, cpu)->seq
){-.-.}-{0:0}, at: psi_task_switch+0x53d/0x810 kernel/sched/psi.c:891
4 locks held by kworker/1:14/3800:
#0: ffff888011c65538 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1: ffffc90004fafd20 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
#2:
ffff888080c460e0
(
&type->s_umount_key#74){++++}-{3:3}, at: flush_old_commits+0xc7/0x2e0 fs/reiserfs/super.c:97
#3: ffff88803f843090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27
2 locks held by kworker/0:16/9373:
#0: ffff888011c66538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2280
#1:
ffffc900106bfd20
(
(work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2282
7 locks held by syz-executor.4/18069:
1 lock held by syz-executor.4/18103:
#0: ffff888081d5d900 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#0: ffff888081d5d900 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: process_measurement+0x435/0x1d60 security/integrity/ima/ima_main.c:241
1 lock held by syz-executor.5/21118:
#0: ffffffff8c943f50 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x285/0x2480 kernel/exit.c:828
1 lock held by syz-executor.5/21119:
#0: ffffffff8c943f50 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x285/0x2480 kernel/exit.c:828
1 lock held by syz-executor.1/21139:
#0: ffffffff8c922af0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x9c/0x4e0 kernel/rcu/tree.c:4018
1 lock held by syz-executor.2/21143:
#0: ffffffff8c943f50 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: copy_process+0x2210/0x3ef0 kernel/fork.c:2299
5 locks held by kvm-nx-lpage-re/21145:
#0: ffffffff8c943d68 (cgroup_mutex){+.+.}-{3:3}, at: cgroup_attach_task_all+0x23/0x150 kernel/cgroup/cgroup-v1.c:61
#1:
ffffffff8c7bc010
(cpu_hotplug_lock){++++}-{0:0}, at: cgroup_attach_task_all+0x28/0x150 kernel/cgroup/cgroup-v1.c:62
#2: ffffffff8c943f50 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: cgroup_attach_task_all+0x34/0x150 kernel/cgroup/cgroup-v1.c:63
#3: ffffffff8c950130 (&cpuset_rwsem){++++}-{0:0}, at: cpuset_can_attach+0x1e9/0x490 kernel/cgroup/cpuset.c:2197
#4:
ffffffff8c922be8
(
rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x280/0x740 kernel/rcu/tree_exp.h:842
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 26 Comm: khungtaskd Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/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 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 21159 Comm: syz-executor.1 Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
RIP: 0010:rb_next+0xa2/0xe0 lib/rbtree.c:517
Code: 48 c1 e8 03 42 80 3c 38 00 74 e3 48 89 df e8 e5 d1 9e fd eb d9 4c 3b 63 08 49 89 dc 75 3d 4c 89 e0 48 c1 e8 03 42 80 3c 38 00 <74> 08 4c 89 e7 e8 c4 d1 9e fd 49 8b 1c 24 48 83 e3 fc 0f 84 79 ff
RSP: 0018:ffffc9000a9e7770 EFLAGS: 00000046
RAX: 1ffff11002d31b42 RBX: 1ffff1100edd7009 RCX: dffffc0000000000
RDX: ffffc9000a9e79a0 RSI: ffff88801698da00 RDI: ffff88801698da10
RBP: ffff888076eb8000 R08: dffffc0000000000 R09: fffffbfff1bc7e0e
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801698da10
R13: ffff888076eb8048 R14: 0000000000000000 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3861f03d00 CR3: 000000001a664000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
rb_erase_cached include/linux/rbtree.h:124 [inline]
__dequeue_entity kernel/sched/fair.c:585 [inline]
set_next_entity+0x27b/0x580 kernel/sched/fair.c:4694
pick_next_task_fair+0x379/0x9c0 kernel/sched/fair.c:7586
__pick_next_task kernel/sched/core.c:5646 [inline]
pick_next_task kernel/sched/core.c:5754 [inline]
__schedule+0x86d/0x4590 kernel/sched/core.c:6336
do_task_dead+0xba/0xc0 kernel/sched/core.c:6390
do_exit+0x1b3e/0x2480 kernel/exit.c:923
do_group_exit+0x144/0x310 kernel/exit.c:994
get_signal+0xc66/0x14e0 kernel/signal.c:2889
arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:865
handle_signal_work kernel/entry/common.c:148 [inline]
exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:172
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f3863a48b29
Code: Unable to access opcode bytes at RIP 0x7f3863a48aff.
RSP: 002b:00007f3861f88178 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007f3863b68128 RCX: 00007f3863a48b29
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f3863b68128
RBP: 00007f3863b68120 R08: 00007f3861f886c0 R09: 00007f3861f886c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f3863b6812c
R13: 000000000000006e R14: 00007ffe3df2d400 R15: 00007ffe3df2d4e8
</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 change 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
Oct 31, 2023, 5:35:16 AM10/31/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