From: syzbot <syzbot+c51f73e78e7e2ce3a31e@syzkaller.appspotmail.com>
To: catalin.marinas@arm.com, coreteam@netfilter.org,
davem@davemloft.net, deller@gmx.de, fw@strlen.de,
jejb@parisc-linux.org, kadlec@blackhole.kfki.hu,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-parisc@vger.kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pablo@netfilter.org, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com
Subject: Re: memory leak in __nf_hook_entries_try_shrink
Date: Mon, 29 Jul 2019 01:16:00 -0700 [thread overview]
Message-ID: <00000000000094699a058ecd8017@google.com> (raw)
In-Reply-To: <0000000000005718ef058b3a0fcf@google.com>
syzbot has bisected this bug to:
commit fc79168a7c75423047d60a033dc4844955ccae0b
Author: Helge Deller <deller@gmx.de>
Date: Wed Apr 13 20:44:54 2016 +0000
parisc: Add syscall tracepoint support
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16ad2cd8600000
start commit: b076173a Merge tag 'selinux-pr-20190612' of git://git.kern..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=15ad2cd8600000
console output: https://syzkaller.appspot.com/x/log.txt?x=11ad2cd8600000
kernel config: https://syzkaller.appspot.com/x/.config?x=cb38d33cd06d8d48
dashboard link: https://syzkaller.appspot.com/bug?extid=c51f73e78e7e2ce3a31e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=105a958ea00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=103c758ea00000
Reported-by: syzbot+c51f73e78e7e2ce3a31e@syzkaller.appspotmail.com
Fixes: fc79168a7c75 ("parisc: Add syscall tracepoint support")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2019-07-29 8:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0000000000005718ef058b3a0fcf@google.com>]
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=00000000000094699a058ecd8017@google.com \
--to=syzbot+c51f73e78e7e2ce3a31e@syzkaller.appspotmail.com \
--cc=catalin.marinas@arm.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=fw@strlen.de \
--cc=jejb@parisc-linux.org \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=rostedt@goodmis.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).