From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Vince Weaver <vincent.weaver@maine.edu>,
syzbot <syzbot+10189b9b0f8c4664badd@syzkaller.appspotmail.com>
Cc: acme@kernel.org, acme@redhat.com,
alexander.shishkin@linux.intel.com, bp@alien8.de,
eranian@google.com, hpa@zytor.com, jolsa@kernel.org,
jolsa@redhat.com, linux-kernel@vger.kernel.org, mingo@kernel.org,
mingo@redhat.com, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
torvalds@linux-foundation.org, x86@kernel.org
Subject: Re: WARNING in perf_reg_value
Date: Wed, 19 Jun 2019 17:15:32 -0400 [thread overview]
Message-ID: <8ec677d7-f891-1c8b-33bd-16506974fafb@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1906191605380.10498@macbook-air>
On 6/19/2019 4:07 PM, Vince Weaver wrote:
> On Wed, 19 Jun 2019, syzbot wrote:
>
>> syzbot found the following crash on:
>>
>> HEAD commit: 0011572c Merge branch 'for-5.2-fixes' of git://git.kernel...
>> git tree: upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=12c38d66a00000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=fa9f7e1b6a8bb586
>> dashboard link: https://syzkaller.appspot.com/bug?extid=10189b9b0f8c4664badd
>> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1434b876a00000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10e6c876a00000
>
> the perf_fuzzer found this issue about a month ago, and patches were
> posted that fixed the issue (I've been unable to reproduce when running
> with a patched kernel).
Here are the patches posted.
https://lkml.org/lkml/2019/5/28/1022
Thanks,
Kan
>
> Any reason they haven't been applied?
>
> Vince
>
next prev parent reply other threads:[~2019-06-19 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 19:47 syzbot
2019-06-19 20:07 ` Vince Weaver
2019-06-19 21:15 ` Liang, Kan [this message]
2019-06-20 12:13 ` Peter Zijlstra
2019-12-08 5:03 ` syzbot
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=8ec677d7-f891-1c8b-33bd-16506974fafb@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzbot+10189b9b0f8c4664badd@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vincent.weaver@maine.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®