From: syzbot <syzbot+23fe48cbe532abffa52e@syzkaller.appspotmail.com>
To: acme@kernel.org, acme@redhat.com,
alexander.shishkin@linux.intel.com, daniel@iogearbox.net,
davem@davemloft.net, jbacik@fb.com, jolsa@redhat.com,
kernel-team@fb.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, mingo@redhat.com, namhyung@kernel.org,
peterz@infradead.org, rostedt@goodmis.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
torvalds@linux-foundation.org, yhs@fb.com
Subject: Re: WARNING in perf_group_attach
Date: Fri, 22 Nov 2019 08:29:00 -0800 [thread overview]
Message-ID: <0000000000004c40290597f1e91e@google.com> (raw)
In-Reply-To: <0000000000001282e1057e14848e@google.com>
syzbot has bisected this bug to:
commit 33ea4b24277b06dbc55d7f5772a46f029600255e
Author: Song Liu <songliubraving@fb.com>
Date: Wed Dec 6 22:45:16 2017 +0000
perf/core: Implement the 'perf_uprobe' PMU
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1038fecae00000
start commit: 0072a0c1 Merge tag 'media/v4.20-4' of git://git.kernel.org..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1238fecae00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1438fecae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=b9cc5a440391cbfd
dashboard link: https://syzkaller.appspot.com/bug?extid=23fe48cbe532abffa52e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=135e93eb400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13189415400000
Reported-by: syzbot+23fe48cbe532abffa52e@syzkaller.appspotmail.com
Fixes: 33ea4b24277b ("perf/core: Implement the 'perf_uprobe' PMU")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-22 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 12:51 WARNING in perf_group_attach syzbot
2019-11-22 16:29 ` syzbot [this message]
2019-11-22 18:22 ` Song Liu
2019-12-08 10:17 ` 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=0000000000004c40290597f1e91e@google.com \
--to=syzbot+23fe48cbe532abffa52e@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jbacik@fb.com \
--cc=jolsa@redhat.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox