[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1452565288.1223.10.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Mon, 11 Jan 2016 18:21:28 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Salam Noureddine <noureddine@...sta.com>
Cc: Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Pali Rohár <pali.rohar@...il.com>,
Network Development <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Sebastian Reichel <sre@...nel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>
Subject: Re: [OOPS] In __netif_receive_skb_core
On Mon, 2016-01-11 at 17:19 -0800, Salam Noureddine wrote:
> It must be that skb->dev was changed to NULL inside of
> __netif_receive_skb_core, otherwise we would have crashed much
> earlier. Also, orig_dev is saved at the beginning. Possibly a device
> is layered on top of the original device.
Please do not top post on netdev / lkml mailing lists.
My guess is a protocol handler queued the skb without calling
skb_share_check()
Powered by blists - more mailing lists