From: syzbot <syzbot+cef9473c7fa0fe8ab95e@syzkaller.appspotmail.com>
To: acme@kernel.org, alexander.shishkin@linux.intel.com,
bhole_prashant_q7@lab.ntt.co.jp, jolsa@redhat.com,
linux-kernel@vger.kernel.org, mingo@kernel.org, mingo@redhat.com,
namhyung@kernel.org, oleg@redhat.com, peterz@infradead.org,
rostedt@goodmis.org, stable@kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
torvalds@linux-foundation.org
Subject: Re: KASAN: use-after-free Read in uprobe_perf_close
Date: Thu, 07 Nov 2019 05:42:08 -0800 [thread overview]
Message-ID: <000000000000ef265b0596c1d48c@google.com> (raw)
In-Reply-To: <001a113f8bf6a9acd90568e8ea59@google.com>
syzbot suspects this bug was fixed by commit:
commit 621b6d2ea297d0fb6030452c5bcd221f12165fcf
Author: Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>
Date: Mon Apr 9 10:03:46 2018 +0000
perf/core: Fix use-after-free in uprobe_perf_close()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1068a38c600000
start commit: 86bbbeba Merge branch 'ras-core-for-linus' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=5e630e8cb6d3da36
dashboard link: https://syzkaller.appspot.com/bug?extid=cef9473c7fa0fe8ab95e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=162240bb800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17a4e0bb800000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: perf/core: Fix use-after-free in uprobe_perf_close()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-07 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 3:01 KASAN: use-after-free Read in uprobe_perf_close syzbot
2019-11-07 13:42 ` syzbot [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=000000000000ef265b0596c1d48c@google.com \
--to=syzbot+cef9473c7fa0fe8ab95e@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bhole_prashant_q7@lab.ntt.co.jp \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stable@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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