From: syzbot <syzbot+b2098bc44728a4efb3e9@syzkaller.appspotmail.com>
To: bsingharora@gmail.com, coreteam@netfilter.org,
davem@davemloft.net, dri-devel@lists.freedesktop.org,
duwe@suse.de, dvyukov@google.com, kaber@trash.net,
kadlec@blackhole.kfki.hu, linaro-mm-sig@lists.linaro.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mingo@redhat.com, mpe@ellerman.id.au, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
rostedt@goodmis.org, sumit.semwal@linaro.org,
syzkaller-bugs@googlegroups.com
Subject: Re: memory leak in dma_buf_ioctl
Date: Thu, 25 Jul 2019 19:34:01 -0700 [thread overview]
Message-ID: <00000000000005dbbc058e8c608d@google.com> (raw)
In-Reply-To: <000000000000b68e04058e6a3421@google.com>
syzbot has bisected this bug to:
commit 04cf31a759ef575f750a63777cee95500e410994
Author: Michael Ellerman <mpe@ellerman.id.au>
Date: Thu Mar 24 11:04:01 2016 +0000
ftrace: Make ftrace_location_range() global
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=154293f4600000
start commit: abdfd52a Merge tag 'armsoc-defconfig' of git://git.kernel...
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=174293f4600000
console output: https://syzkaller.appspot.com/x/log.txt?x=134293f4600000
kernel config: https://syzkaller.appspot.com/x/.config?x=d31de3d88059b7fa
dashboard link: https://syzkaller.appspot.com/bug?extid=b2098bc44728a4efb3e9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12526e58600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=161784f0600000
Reported-by: syzbot+b2098bc44728a4efb3e9@syzkaller.appspotmail.com
Fixes: 04cf31a759ef ("ftrace: Make ftrace_location_range() global")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2019-07-26 2:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000b68e04058e6a3421@google.com>
2019-07-26 2:34 ` syzbot [this message]
2019-07-26 2:46 ` memory leak in dma_buf_ioctl 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=00000000000005dbbc058e8c608d@google.com \
--to=syzbot+b2098bc44728a4efb3e9@syzkaller.appspotmail.com \
--cc=bsingharora@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=duwe@suse.de \
--cc=dvyukov@google.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=rostedt@goodmis.org \
--cc=sumit.semwal@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).