From: syzbot <syzbot+5134cdf021c4ed5aaa5f@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, catalin.marinas@arm.com,
davem@davemloft.net, dvyukov@google.com, jack@suse.com,
kirill.shutemov@linux.intel.com, koct9i@gmail.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-rdma@vger.kernel.org, neilb@suse.de,
netdev@vger.kernel.org, rds-devel@oss.oracle.com,
ross.zwisler@linux.intel.com, santosh.shilimkar@oracle.com,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
willy@linux.intel.com
Subject: Re: memory leak in rds_send_probe
Date: Tue, 23 Jul 2019 15:17:00 -0700 [thread overview]
Message-ID: <00000000000034c84a058e608d45@google.com> (raw)
In-Reply-To: <000000000000ad1dfe058e5b89ab@google.com>
syzbot has bisected this bug to:
commit af49a63e101eb62376cc1d6bd25b97eb8c691d54
Author: Matthew Wilcox <willy@linux.intel.com>
Date: Sat May 21 00:03:33 2016 +0000
radix-tree: change naming conventions in radix_tree_shrink
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=176528c8600000
start commit: c6dd78fc Merge branch 'x86-urgent-for-linus' of git://git...
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=14e528c8600000
console output: https://syzkaller.appspot.com/x/log.txt?x=10e528c8600000
kernel config: https://syzkaller.appspot.com/x/.config?x=8de7d700ea5ac607
dashboard link: https://syzkaller.appspot.com/bug?extid=5134cdf021c4ed5aaa5f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=145df0c8600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=170001f4600000
Reported-by: syzbot+5134cdf021c4ed5aaa5f@syzkaller.appspotmail.com
Fixes: af49a63e101e ("radix-tree: change naming conventions in
radix_tree_shrink")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2019-07-23 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000ad1dfe058e5b89ab@google.com>
2019-07-23 22:17 ` syzbot [this message]
2019-07-23 22:23 ` Andrew Morton
2019-07-23 23:25 ` Eric Biggers
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=00000000000034c84a058e608d45@google.com \
--to=syzbot+5134cdf021c4ed5aaa5f@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=jack@suse.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=ross.zwisler@linux.intel.com \
--cc=santosh.shilimkar@oracle.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@linux.intel.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