syzbot


suspicious RCU usage at arch/x86/kvm/x86.c:LINE

Status: closed as invalid on 2017/08/15 05:48
First crash: 2985d, last: 2985d
Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream suspicious RCU usage at arch/x86/kvm/x86.c:LINE (2) -1 4 2940d 2900d 0/29 closed as invalid on 2017/10/31 09:49

Sample crash report:
=============================
WARNING: suspicious RCU usage
4.13.0-rc4+ #23 Not tainted
sctp: [Deprecated]: syz-executor4 (pid 6539) Use of int in max_burst socket option.
Use struct sctp_assoc_value instead
sctp: [Deprecated]: syz-executor4 (pid 6546) Use of int in max_burst socket option.
Use struct sctp_assoc_value instead
netlink: 16 bytes leftover after parsing attributes in process `syz-executor1'.
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pig=6572 comm=syz-executor1
*** Guest State ***
CR0: actual=0x0000000080000031, shadow=0x0000000060000010, gh_mask=fffffffffffffff7
CR4: actual=0x0000000000002051, shadow=0x0000000000000000, gh_mask=fffffffffffff871
CR3 = 0x00000000fffbc000
RSP = 0x000000000000fffa  RIP = 0x0000000000000000
RFLAGS=0x00033000         DR7 = 0x0000000000000402
Sysenter RSP=0000000000000000 CS:RIP=0000:0000000000000000
CS:   sel=0x0000, attr=0x000f3, limit=0x0000ffff, base=0x0000000000000000
DS:   sel=0x0000, attr=0x000f3, limit=0x0000ffff, base=0x0000000000000000
SS:   sel=0x0000, attr=0x000f3, limit=0x0000ffff, base=0x0000000000000000
ES:   sel=0x0000, attr=0x000f3, limit=0x0000ffff, base=0x0000000000000000
FS:   sel=0x0000, attr=0x000f3, limit=0x0000ffff, base=0x0000000000000000
GS:   sel=0x0000, attr=0x000f3, limit=0x0000ffff, base=0x0000000000000000
GDTR:                           limit=0x0000ffff, base=0x0000000000000000
LDTR: sel=0x0000, attr=0x00082, limit=0x0000ffff, base=0x0000000000000000
IDTR:                           limit=0x0000ffff, base=0x0000000000000000
TR:   sel=0x0000, attr=0x0008b, limit=0x00002088, base=0x0000000000000000
EFER =     0x0000000000000000  PAT = 0x0007040600070406
DebugCtl = 0x0000000000000000  DebugExceptions = 0x0000000000000000
Interruptibility = 00000000  ActivityState = 00000000
*** Host State ***
RIP = 0xffffffff811bb0b6  RSP = 0xffff8801d11ef4c8
CS=0010 SS=0018 DS=0000 ES=0000 FS=0000 GS=0000 TR=0040
FSBase=00007fa7f0ae5700 GSBase=ffff8801dc100000 TRBase=ffff8801dc122c80
GDTBase=ffffffffff576000 IDTBase=ffffffffff57b000
CR0=0000000080050033 CR3=00000001a1c00000 CR4=00000000001426e0
Sysenter RSP=0000000000000000 CS:RIP=0010:ffffffff844a23d0
EFER = 0x0000000000000d01  PAT = 0x0000000000000000
*** Control State ***
PinBased=0000003f CPUBased=b6a1edfa SecondaryExec=0000004b
EntryControls=0000d1ff ExitControls=0023efff
ExceptionBitmap=ffffbfff PFECmask=00000000 PFECmatch=00000000
VMEntry: intr_info=00000000 errcode=00000000 ilen=00000000
VMExit: intr_info=00000000 errcode=00000000 ilen=00000000
        reason=80000021 qualification=0000000000000000
IDTVectoring: info=00000000 errcode=00000000
TSC Offset = 0xffffffe289c014d6
TPR Threshold = 0x00
EPT pointer = 0x00000001c269d01e
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=62445 sclass=netlink_route_socket pig=6584 comm=syz-executor5
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=62445 sclass=netlink_route_socket pig=6594 comm=syz-executor5
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6589 at arch/x86/kvm/x86.c:7226 kvm_arch_vcpu_ioctl_run+0x213/0x5870 arch/x86/kvm/x86.c:7226

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2017/08/07 19:09 upstream aae4e7a8bc44 77a9ec9b .config console log report ci-upstream-kasan-gce
* Struck through repros no longer work on HEAD.