From: syzbot <syzbot+e93c1d9ae19a0236289c@syzkaller.appspotmail.com>
To: coreteam@netfilter.org, davem@davemloft.net, fw@strlen.de,
kadlec@netfilter.org, kuba@kernel.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: Mon, 23 Mar 2020 03:39:02 -0700 [thread overview]
Message-ID: <0000000000005fc4c505a1833ed3@google.com> (raw)
In-Reply-To: <000000000000b6da7b059c8110c4@google.com>
syzbot suspects this bug was fixed by commit:
commit a7da92c2c8a1faf253a3b3e292fda6910deba540
Author: Florian Westphal <fw@strlen.de>
Date: Mon Feb 3 12:06:18 2020 +0000
netfilter: flowtable: skip offload setup if disabled
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1522646be00000
start commit: 0a44cac8 Merge tag 'dma-mapping-5.6' of git://git.infradea..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=31018567b8f0fc70
dashboard link: https://syzkaller.appspot.com/bug?extid=e93c1d9ae19a0236289c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126c7e09e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1208fdd9e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: netfilter: flowtable: skip offload setup if disabled
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-03-23 10:39 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
2020-03-23 10:39 ` syzbot [this message]
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=0000000000005fc4c505a1833ed3@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=kuba@kernel.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.