From: syzbot <syzbot+46a4ad33f345d1dd346e@syzkaller.appspotmail.com>
To: coreteam@netfilter.org, davem@davemloft.net, fw@strlen.de,
kadlec@blackhole.kfki.hu, kadlec@netfilter.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in dccp_timeout_nlattr_to_obj
Date: Mon, 06 Jan 2020 17:28:01 -0800 [thread overview]
Message-ID: <000000000000d04359059b82afd9@google.com> (raw)
In-Reply-To: <0000000000009cd5e0059b7eb836@google.com>
syzbot has bisected this bug to:
commit dd2934a95701576203b2f61e8ded4e4a2f9183ea
Author: Florian Westphal <fw@strlen.de>
Date: Mon Sep 17 10:02:54 2018 +0000
netfilter: conntrack: remove l3->l4 mapping information
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10957485e00000
start commit: d89091a4 macb: Don't unregister clks unconditionally
git tree: net
final crash: https://syzkaller.appspot.com/x/report.txt?x=12957485e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=14957485e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=f2f3ef188b7e16cf
dashboard link: https://syzkaller.appspot.com/bug?extid=46a4ad33f345d1dd346e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12ff2869e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16693751e00000
Reported-by: syzbot+46a4ad33f345d1dd346e@syzkaller.appspotmail.com
Fixes: dd2934a95701 ("netfilter: conntrack: remove l3->l4 mapping
information")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-01-07 1:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 20:44 general protection fault in dccp_timeout_nlattr_to_obj syzbot
2020-01-06 22:34 ` [PATCH nf] netfilter: conntrack: dccp, sctp: handle null timeout argument Florian Westphal
2020-01-08 22:32 ` Pablo Neira Ayuso
2020-01-07 1:28 ` 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=000000000000d04359059b82afd9@google.com \
--to=syzbot+46a4ad33f345d1dd346e@syzkaller.appspotmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=kadlec@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 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.