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

8 views
Skip to first unread message

syzbot

unread,
Oct 31, 2017, 5:39:54 AM10/31/17
to syzkaller-upst...@googlegroups.com
Hello,

syzkaller hit the following crash on
720bbe532b7c8f5613b48dea627fc58ed9ace707
git://git.cmpxchg.org/linux-mmots.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.


CC: [h...@zytor.com k...@vger.kernel.org linux-...@vger.kernel.org
mi...@redhat.com pbon...@redhat.com rkr...@redhat.com tg...@linutronix.de
x...@kernel.org]

WARNING: suspicious RCU usage
4.13.0-mm1+ #7 Not tainted
-----------------------------
*** Guest State ***
CR0: actual=0x0000000080000031, shadow=0x0000000060000010,
gh_mask=fffffffffffffff7
CR4: actual=0x0000000000002051, shadow=0x0000000000000000,
gh_mask=ffffffffffffe871
CR3 = 0x00000000fffbc000
RSP = 0x000000000000fffa RIP = 0x0000000000000000
RFLAGS=0x00023000 DR7 = 0x0000000000000400
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 = 0xffffffff811b8bff RSP = 0xffff8801d8b7f4c8
CS=0010 SS=0018 DS=0000 ES=0000 FS=0000 GS=0000 TR=0040
FSBase=00007fb7f3a8f700 GSBase=ffff8801db300000 TRBase=ffff8801db323100
GDTBase=ffffffffff576000 IDTBase=ffffffffff57b000
CR0=0000000080050033 CR3=00000001c1881000 CR4=00000000001426e0
Sysenter RSP=0000000000000000 CS:RIP=0010:ffffffff84d450b0
EFER = 0x0000000000000d01 PAT = 0x0000000000000000
*** Control State ***
PinBased=0000003f CPUBased=b699edfa SecondaryExec=00000042
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=00000005
reason=80000021 qualification=0000000000000000
IDTVectoring: info=00000000 errcode=00000000
TSC Offset = 0xffffffb20e313c87
EPT pointer = 0x00000001c564e01e
------------[ cut here ]------------
WARNING: CPU: 0 PID: 16668 at arch/x86/kvm/x86.c:7256
kvm_arch_vcpu_ioctl_run+0x213/0x5a30 arch/x86/kvm/x86.c:7256


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
Please credit me with: Reported-by: syzbot

syzbot will keep track of this bug report.
Once a fix for this bug is committed, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line.
To upstream this report, please reply with:
#syz upstream
config.txt
raw.log

Dmitry Vyukov

unread,
Oct 31, 2017, 5:49:38 AM10/31/17
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
That's all corrupted reports:

#syz invalid

On Tue, Oct 31, 2017 at 12:39 PM, syzbot
<bot+86427303f362bb133f...@syzkaller.appspotmail.com>
wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/94eb2c19df1863c266055cd4894d%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages