All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: syzbot <syzbot+9cbc6bed3a22f1d37395@syzkaller.appspotmail.com>
Cc: Alexander Lobakin <alobakin@pm.me>,
	Borislav Petkov <bp@alien8.de>,
	Daniel Borkmann <daniel@iogearbox.net>,
	"Anvin, H. Peter" <hpa@zytor.com>,
	Jim Mattson <jmattson@google.com>,
	John Fastabend <john.fastabend@gmail.com>,
	Joerg Roedel <joro@8bytes.org>, kvm <kvm@vger.kernel.org>,
	"Kernel Mailing List, Linux" <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Networking <netdev@vger.kernel.org>,
	Sean Christopherson <seanjc@google.com>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	xuanzhuo@linux.alibaba.com
Subject: Re: [syzbot] WARNING: suspicious RCU usage (5)
Date: Thu, 23 Jun 2022 10:54:37 +0200	[thread overview]
Message-ID: <CABgObfarsDqG3g1L561CHvg3j0aROSz5zdcB5kOibcjbLN_y9g@mail.gmail.com> (raw)
In-Reply-To: <0000000000008b8cd205e2187ea2@google.com>

#syz fix: x86/kvm: Fix broken irq restoration in kvm_wait

On Thu, Jun 23, 2022 at 9:35 AM syzbot
<syzbot+9cbc6bed3a22f1d37395@syzkaller.appspotmail.com> wrote:
>
> syzbot has bisected this issue to:
>
> commit c2ff53d8049f30098153cd2d1299a44d7b124c57
> Author: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> Date:   Thu Feb 18 20:50:02 2021 +0000
>
>     net: Add priv_flags for allow tx skb without linear
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11596838080000
> start commit:   a5b00f5b78b7 Merge branch 'hns3-fixres'
> git tree:       net
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=13596838080000
> console output: https://syzkaller.appspot.com/x/log.txt?x=15596838080000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=20ac3e0ebf0db3bd
> dashboard link: https://syzkaller.appspot.com/bug?extid=9cbc6bed3a22f1d37395
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=143b22abf00000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=125194eff00000
>
> Reported-by: syzbot+9cbc6bed3a22f1d37395@syzkaller.appspotmail.com
> Fixes: c2ff53d8049f ("net: Add priv_flags for allow tx skb without linear")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>


      parent reply	other threads:[~2022-06-23  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 22:56 [syzbot] WARNING: suspicious RCU usage (5) syzbot
2022-06-23  7:35 ` syzbot
2022-06-23  8:22   ` Xuan Zhuo
2022-06-23  8:54   ` Paolo Bonzini [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=CABgObfarsDqG3g1L561CHvg3j0aROSz5zdcB5kOibcjbLN_y9g@mail.gmail.com \
    --to=pbonzini@redhat.com \
    --cc=alobakin@pm.me \
    --cc=bp@alien8.de \
    --cc=daniel@iogearbox.net \
    --cc=hpa@zytor.com \
    --cc=jmattson@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=seanjc@google.com \
    --cc=syzbot+9cbc6bed3a22f1d37395@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.com \
    --cc=x86@kernel.org \
    --cc=xuanzhuo@linux.alibaba.com \
    /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.