[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170911060453.6rpx5z3vj25qpcwn@unicorn.suse.cz>
Date: Mon, 11 Sep 2017 08:04:53 +0200
From: Michal Kubecek <mkubecek@...e.cz>
To: Dison River <pwn2river@...il.com>
Cc: davem@...emloft.net, edumazet@...gle.com, daniel@...earbox.net,
alexander.h.duyck@...el.com, dsa@...ulusnetworks.com,
Jakub Kicinski <jakub.kicinski@...ronome.com>, me@...in.cc,
stephen@...workplumber.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, security@...nel.org,
syzkaller@...glegroups.com
Subject: Re: WARNING in skb_warn_bad_offload
On Mon, Sep 11, 2017 at 12:20:32PM +0800, Dison River wrote:
> I found a warning while fuzzing with Syzkaller on linux 4.13-rc6 on
> x86_64. The full stack trace is below:
>
> ------------[ cut here ]------------
> WARNING: CPU: 3 PID: 32413 at net/core/dev.c:2592
> skb_warn_bad_offload+0x2a9/0x380 net/core/dev.c:2587
> Kernel panic - not syncing: panic_on_warn set ...
>
> CPU: 3 PID: 32413 Comm: syz-executor3 Not tainted 4.13.0-rc6+ #1
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
> Call Trace:
Are you sure you didn't omit something? This WARN() check should write
some useful information but I can't see it in your mail:
WARN(1, "%s: caps=(%pNF, %pNF) len=%d data_len=%d gso_size=%d "
"gso_type=%d ip_summed=%d\n",
name, dev ? &dev->features : &null_features,
skb->sk ? &skb->sk->sk_route_caps : &null_features,
skb->len, skb->data_len, skb_shinfo(skb)->gso_size,
skb_shinfo(skb)->gso_type, skb->ip_summed);
Michal Kubecek
Powered by blists - more mailing lists