From: syzbot <syzbot+e93c1d9ae19a0236289c@syzkaller.appspotmail.com>
To: coreteam@netfilter.org, davem@davemloft.net, fw@strlen.de,
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 nf_flow_table_offload_setup
Date: Wed, 22 Jan 2020 08:24:01 -0800 [thread overview]
Message-ID: <000000000000cf992f059cbcf362@google.com> (raw)
In-Reply-To: <000000000000b6da7b059c8110c4@google.com>
syzbot has bisected this bug to:
commit a7965d58ddab0253ddfae58bd5c7d2de46ef0f76
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Mon Jan 13 18:02:22 2020 +0000
netfilter: flowtable: add nf_flow_table_offload_cmd()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17ea59c9e00000
start commit: 4f2c17e0 Merge branch 'master' of git://git.kernel.org/pub..
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=141a59c9e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=101a59c9e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7f93900a7904130d
dashboard link: https://syzkaller.appspot.com/bug?extid=e93c1d9ae19a0236289c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=166fea6ee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=108d6185e00000
Reported-by: syzbot+e93c1d9ae19a0236289c@syzkaller.appspotmail.com
Fixes: a7965d58ddab ("netfilter: flowtable: add nf_flow_table_offload_cmd()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-01-22 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 16:57 general protection fault in nf_flow_table_offload_setup syzbot
2020-01-22 16:24 ` syzbot [this message]
2020-03-23 10:39 ` syzbot
2020-03-23 11:07 ` Florian Westphal
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=000000000000cf992f059cbcf362@google.com \
--to=syzbot+e93c1d9ae19a0236289c@syzkaller.appspotmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--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.