From: syzbot <syzbot+eab6e18f95a9fe69005e@syzkaller.appspotmail.com>
To: acme@kernel.org, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, linux-kernel@vger.kernel.org, mingo@redhat.com,
namhyung@kernel.org, oleg@redhat.com, peterz@infradead.org,
ravi.bangoria@linux.ibm.com, rostedt@goodmis.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in delayed_uprobe_remove
Date: Thu, 21 Mar 2019 04:03:00 -0700 [thread overview]
Message-ID: <000000000000737c07058498aea1@google.com> (raw)
In-Reply-To: <000000000000ec1b3805799d0a56@google.com>
syzbot has bisected this bug to:
commit a6ca88b241d5e929e6e60b12ad8cd288f0ffa256
Author: Song Liu <songliubraving@fb.com>
Date: Tue Oct 2 05:36:36 2018 +0000
trace_uprobe: support reference counter in fd-based uprobe
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12c86993200000
start commit: a6ca88b2 trace_uprobe: support reference counter in fd-bas..
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=11c86993200000
console output: https://syzkaller.appspot.com/x/log.txt?x=16c86993200000
kernel config: https://syzkaller.appspot.com/x/.config?x=2a22859d870756c1
dashboard link: https://syzkaller.appspot.com/bug?extid=eab6e18f95a9fe69005e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137174f5400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1278485d400000
Reported-by: syzbot+eab6e18f95a9fe69005e@syzkaller.appspotmail.com
Fixes: a6ca88b241d5 ("trace_uprobe: support reference counter in fd-based
uprobe")
next prev parent reply other threads:[~2019-03-21 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 16:38 general protection fault in delayed_uprobe_remove syzbot
2018-11-03 19:16 ` syzbot
2019-03-21 11:03 ` syzbot [this message]
2019-03-21 16:18 ` Oleg Nesterov
2019-03-21 16:26 ` Steven Rostedt
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=000000000000737c07058498aea1@google.com \
--to=syzbot+eab6e18f95a9fe69005e@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.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.