From: Florian Westphal <fw@strlen.de>
To: syzbot <syzbot+e783f671527912cd9403@syzkaller.appspotmail.com>
Cc: coreteam@netfilter.org, davem@davemloft.net, fw@strlen.de,
kadlec@blackhole.kfki.hu, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org
Subject: Re: general protection fault in ip6t_do_table
Date: Sun, 28 Jan 2018 22:55:41 +0100 [thread overview]
Message-ID: <20180128215541.GC5906@breakpoint.cc> (raw)
In-Reply-To: <001a1134eab4b849a50563c844fd@google.com>
syzbot <syzbot+e783f671527912cd9403@syzkaller.appspotmail.com> wrote:
> CPU: 0 PID: 3675 Comm: syzkaller168273 Not tainted 4.15.0-rc9+ #283
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> RIP: 0010:ip6t_do_table+0x12de/0x19d0 net/ipv6/netfilter/ip6_tables.c:360
> RSP: 0018:ffff8801db206c58 EFLAGS: 00010246
> RAX: 0000000000000000 RBX: ffff8801d9aafb80 RCX: ffffffff84d30352
> RDX: 0000000000000100 RSI: 0000000000000000 RDI: ffff8801d9aafcde
> RBP: ffff8801db206e60 R08: 1ffff1003b640d54 R09: 0000000000000000
> R10: 00000000000000d0 R11: 0000000000000000 R12: 0000000000000001
> R13: 0000000000000000 R14: dffffc0000000000 R15: ffff8801d9aafc50
> FS: 0000000000a5d880(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00000000209f1000 CR3: 00000001bc9f8001 CR4: 00000000001606f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <IRQ>
> ip6table_security_hook+0x65/0x80 net/ipv6/netfilter/ip6table_security.c:45
In case noone else can look at this I'll investigate this next friday
(currently travelling).
prev parent reply other threads:[~2018-01-28 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 20:58 general protection fault in ip6t_do_table syzbot
2018-01-28 21:55 ` Florian Westphal [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=20180128215541.GC5906@breakpoint.cc \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzbot+e783f671527912cd9403@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yoshfuji@linux-ipv6.org \
/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.