BUG: soft lockup in __perf_sw_event

6 views
Skip to first unread message

syzbot

unread,
Dec 15, 2020, 2:45:10 PM12/15/20
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 30fc3020 BACKPORT: mm/gup: Remove enfornced COW mechanism
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=178c2287500000
kernel config: https://syzkaller.appspot.com/x/.config?x=3f87a6a62e174867
dashboard link: https://syzkaller.appspot.com/bug?extid=39fa2de4731f5366c85b
compiler: Android (6032204 based on r370808) clang version 10.0.1 (https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+39fa2d...@syzkaller.appspotmail.com

watchdog: BUG: soft lockup - CPU#1 stuck for 134s! [syz-executor.4:6442]
Modules linked in:
CPU: 1 PID: 6442 Comm: syz-executor.4 Not tainted 5.4.83-syzkaller-00110-g30fc30201c19 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:pvclock_scale_delta arch/x86/include/asm/pvclock.h:68 [inline]
RIP: 0010:__pvclock_read_cycles arch/x86/include/asm/pvclock.h:85 [inline]
RIP: 0010:pvclock_clocksource_read+0x128/0x6b0 arch/x86/kernel/pvclock.c:76
Code: 04 20 84 c0 0f 85 b4 02 00 00 0f b6 06 89 c1 f6 d9 48 89 ea 48 d3 ea 89 c1 48 d3 e5 84 c0 48 0f 48 ea 48 89 5c 24 68 48 89 e8 <48> f7 64 24 68 48 0f ac d0 20 48 89 44 24 50 49 8d 6f 07 4c 89 f8
RSP: 0018:ffff8881a484ee58 EFLAGS: 00000286 ORIG_RAX: ffffffffffffff13
RAX: 00000089b2ae32e1 RBX: 00000000de9bd37a RCX: 00000000000000ff
RDX: 00000089b2ae32e1 RSI: ffffffff85f3805c RDI: ffffffff85f3805d
RBP: 00000089b2ae32e1 R08: ffffffff85f38048 R09: ffffffff85f38058
R10: ffffffff85f38043 R11: 1ffffffff0be7008 R12: dffffc0000000000
R13: ffffffff85f38040 R14: 0000000000000006 R15: ffffffff85f38050
FS: 00007f206724c700(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000053 CR3: 00000001e4bdc000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
kvm_clock_read arch/x86/kernel/kvmclock.c:90 [inline]
kvm_sched_clock_read+0x15/0x40 arch/x86/kernel/kvmclock.c:102
paravirt_sched_clock arch/x86/include/asm/paravirt.h:22 [inline]
sched_clock+0x36/0x40 arch/x86/kernel/tsc.c:245
sched_clock_cpu+0x18/0x3b0 kernel/sched/clock.c:371
local_clock include/linux/sched/clock.h:84 [inline]
cpu_clock_event_update kernel/events/core.c:9698 [inline]
cpu_clock_event_read+0x17/0x50 kernel/events/core.c:9731
perf_output_read_group kernel/events/core.c:6341 [inline]
perf_output_read+0xf4f/0x1480 kernel/events/core.c:6380
perf_output_sample+0x354/0x1e20 kernel/events/core.c:6422
__perf_event_output kernel/events/core.c:6749 [inline]
perf_event_output_forward+0x140/0x1b0 kernel/events/core.c:6763
__perf_event_overflow+0x1b9/0x340 kernel/events/core.c:8237
do_perf_sw_event kernel/events/core.c:8454 [inline]
___perf_sw_event+0x3bc/0x4c0 kernel/events/core.c:8485
__perf_sw_event+0x12e/0x220 kernel/events/core.c:8497
page_fault+0x2f/0x40 arch/x86/entry/entry_64.S:1203
RIP: 0010:copy_user_enhanced_fast_string+0xe/0x30 arch/x86/lib/copy_user_64.S:205
Code: 89 d1 c1 e9 03 83 e2 07 f3 48 a5 89 d1 f3 a4 31 c0 0f 1f 00 c3 0f 1f 80 00 00 00 00 0f 1f 00 83 fa 40 0f 82 70 ff ff ff 89 d1 <f3> a4 31 c0 0f 1f 00 c3 66 2e 0f 1f 84 00 00 00 00 00 89 d1 f3 a4
RSP: 0018:ffff8881a484f8c0 EFLAGS: 00010206
RAX: ffffffff82234001 RBX: 0000000020facfcb RCX: 0000000000000fcb
RDX: 0000000000008000 RSI: 0000000020fac000 RDI: ffff888196527035
RBP: ffff888196520000 R08: dffffc0000000000 R09: ffffed1032ca5000
R10: 0000000000000000 R11: 0000000000000000 R12: 00007ffffffff000
R13: 0000000000008000 R14: 0000000020fa4fcb R15: ffff888196520000
copy_user_generic arch/x86/include/asm/uaccess_64.h:37 [inline]
raw_copy_from_user arch/x86/include/asm/uaccess_64.h:71 [inline]
copyin+0x8e/0xb0 lib/iov_iter.c:151
_copy_from_iter_full+0x194/0x860 lib/iov_iter.c:769
copy_from_iter_full include/linux/uio.h:156 [inline]
skb_do_copy_data_nocache+0x134/0x370 include/net/sock.h:2006
skb_copy_to_page_nocache include/net/sock.h:2032 [inline]
tcp_sendmsg_locked+0x18ee/0x3f20 net/ipv4/tcp.c:1347
tcp_sendmsg+0x2c/0x40 net/ipv4/tcp.c:1445
sock_sendmsg_nosec net/socket.c:638 [inline]
sock_sendmsg net/socket.c:658 [inline]
__sys_sendto+0x4f6/0x6c0 net/socket.c:1953
__do_sys_sendto net/socket.c:1965 [inline]
__se_sys_sendto net/socket.c:1961 [inline]
__x64_sys_sendto+0xda/0xf0 net/socket.c:1961
do_syscall_64+0xcb/0x150 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45e159
Code: 0d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f206724bc68 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffda RBX: 0000000000000006 RCX: 000000000045e159
RDX: ffffffffffffffef RSI: 0000000020d7cfcb RDI: 0000000000000004
RBP: 000000000119bfd8 R08: 0000000000000000 R09: 0000000000000053
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000119bf8c
R13: 00007ffd1ed99bff R14: 00007f206724c9c0 R15: 000000000119bf8c
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:60 [inline]
NMI backtrace for cpu 0 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:103 [inline]
NMI backtrace for cpu 0 skipped: idling at default_idle+0x1f/0x30 arch/x86/kernel/process.c:572


---
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

unread,
Apr 27, 2021, 1:47:18 PM4/27/21
to syzkaller-a...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages