All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: syzbot <syzbot+71271244f206d17f6441@syzkaller.appspotmail.com>,
	bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	jarkko@kernel.org, jmattson@google.com, joro@8bytes.org,
	kan.liang@linux.intel.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-sgx@vger.kernel.org,
	mingo@redhat.com, pbonzini@redhat.com, peterz@infradead.org,
	seanjc@google.com, steve.wahl@hpe.com,
	syzkaller-bugs@googlegroups.com, vkuznets@redhat.com,
	wanpengli@tencent.com, x86@kernel.org
Subject: Re: [syzbot] WARNING in x86_emulate_instruction
Date: Fri, 28 May 2021 00:52:03 +0200	[thread overview]
Message-ID: <87v9737pt8.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <000000000000f3fc9305c2e24311@google.com>

On Fri, May 21 2021 at 19:52, syzbot wrote:

> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:    8ac91e6c Merge tag 'for-5.13-rc2-tag' of git://git.kernel...
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=16a80fc7d00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=dddb87edd6431081
> dashboard link: https://syzkaller.appspot.com/bug?extid=71271244f206d17f6441
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12d1f89bd00000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=134683fdd00000
>
> The issue was bisected to:
>
> commit 9a7832ce3d920426a36cdd78eda4b3568d4d09e3
> Author: Steve Wahl <steve.wahl@hpe.com>
> Date:   Fri Jan 8 15:35:49 2021 +0000
>
>     perf/x86/intel/uncore: With > 8 nodes, get pci bus die id from NUMA info
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=152bf9b3d00000
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=172bf9b3d00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=132bf9b3d00000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+71271244f206d17f6441@syzkaller.appspotmail.com
> Fixes: 9a7832ce3d92 ("perf/x86/intel/uncore: With > 8 nodes, get pci bus die id from NUMA info")

So this is stale for a week now. It's fully reproducible and nobody
can't be bothered to look at that?

What's wrong with you people?

Thanks,

        tglx

  reply	other threads:[~2021-05-27 22:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22  2:52 [syzbot] WARNING in x86_emulate_instruction syzbot
2021-05-27 22:52 ` Thomas Gleixner [this message]
2021-05-27 23:21   ` Paolo Bonzini
2021-05-27 23:56     ` Thomas Gleixner
2021-05-28  0:34       ` Wanpeng Li
2021-06-07 10:34         ` Dmitry Vyukov
2021-06-07 13:58           ` Paolo Bonzini

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=87v9737pt8.ffs@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jarkko@kernel.org \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kan.liang@linux.intel.com \
    --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=peterz@infradead.org \
    --cc=seanjc@google.com \
    --cc=steve.wahl@hpe.com \
    --cc=syzbot+71271244f206d17f6441@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.com \
    --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.