From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+4f6eb69074ff62a1a33b@syzkaller.appspotmail.com>
Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
jarkko@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sgx@vger.kernel.org,
mingo@redhat.com, pbonzini@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: [syzbot] BUG: unable to handle kernel paging request in kvm_arch_hardware_enable
Date: Tue, 16 Aug 2022 14:04:18 +0000 [thread overview]
Message-ID: <Yvuj4ugWYpthUwhj@google.com> (raw)
In-Reply-To: <0000000000009700a805e657c8fa@google.com>
On Tue, Aug 16, 2022, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 7ebfc85e2cd7 Merge tag 'net-6.0-rc1' of git://git.kernel.o..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=13d10985080000
> kernel config: https://syzkaller.appspot.com/x/.config?x=20bc0b329895d963
> dashboard link: https://syzkaller.appspot.com/bug?extid=4f6eb69074ff62a1a33b
> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1538e0b5080000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=112756f3080000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+4f6eb69074ff62a1a33b@syzkaller.appspotmail.com
Fix posted[*], apparently the sybot id changes when bugs get forwarded upstream.
[*] https://lore.kernel.org/all/20220816053937.2477106-2-seanjc@google.com
prev parent reply other threads:[~2022-08-16 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 8:46 [syzbot] BUG: unable to handle kernel paging request in kvm_arch_hardware_enable syzbot
2022-08-16 14:04 ` Sean Christopherson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yvuj4ugWYpthUwhj@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=syzbot+4f6eb69074ff62a1a33b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.