From: Sean Christopherson <seanjc@google•com>
To: syzbot <syzbot+4e697fe80a31aa7efe21@syzkaller•appspotmail.com>
Cc: changbin.du@intel•com, christian.brauner@ubuntu•com,
daniel@iogearbox•net, davem@davemloft•net, edumazet@google•com,
hkallweit1@gmail•com, kuba@kernel•org, kvm@vger•kernel.org,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
pbonzini@redhat•com, syzkaller-bugs@googlegroups•com,
yajun.deng@linux•dev
Subject: Re: [syzbot] WARNING in kvm_mmu_notifier_invalidate_range_start
Date: Tue, 28 Dec 2021 22:26:16 +0000 [thread overview]
Message-ID: <YcuPCI+Nq2ixPGPD@google.com> (raw)
In-Reply-To: <000000000000ef6c6c05d437c830@google.com>
On Tue, Dec 28, 2021, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: ea586a076e8a Add linux-next specific files for 20211224
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=12418ea5b00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a9c4e3dde2c568fb
> dashboard link: https://syzkaller.appspot.com/bug?extid=4e697fe80a31aa7efe21
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15724985b00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d1aedbb00000
>
> The issue was bisected to:
>
> commit e4b8954074f6d0db01c8c97d338a67f9389c042f
> Author: Eric Dumazet <edumazet@google•com>
> Date: Tue Dec 7 01:30:37 2021 +0000
>
> netlink: add net device refcount tracker to struct ethnl_req_info
Heh, while I'd love to blame someone else, there's zero chance this is the
offending commit. The WARN repros on kvm/queue, it's likely related to the KVM
memslot changes queued for 5.17. I'll take a look.
next prev parent reply other threads:[~2021-12-28 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 17:02 [syzbot] WARNING in kvm_mmu_notifier_invalidate_range_start syzbot
2021-12-28 22:26 ` Sean Christopherson [this message]
2021-12-29 19:55 ` Mike Kravetz
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=YcuPCI+Nq2ixPGPD@google.com \
--to=seanjc@google$(echo .)com \
--cc=changbin.du@intel$(echo .)com \
--cc=christian.brauner@ubuntu$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hkallweit1@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pbonzini@redhat$(echo .)com \
--cc=syzbot+4e697fe80a31aa7efe21@syzkaller$(echo .)appspotmail.com \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=yajun.deng@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox