From: John Fastabend <john.r.fastabend@intel.com>
To: Ben Greear <greearb@candelatech.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: Reproducible VLAN/e1000e crash in 2.6.36 vanilla.
Date: Mon, 25 Oct 2010 14:34:35 -0700 [thread overview]
Message-ID: <4CC5F7EB.7010307@intel.com> (raw)
In-Reply-To: <4CC5F40D.8050302@candelatech.com>
On 10/25/2010 2:18 PM, Ben Greear wrote:
> On 10/25/2010 10:57 AM, Ben Greear wrote:
>>
>> To re-create, setup 2 802.1q vlans on different physical interfaces on
>> the same system,
>> set up routing rules such that send-to-self works, and pass traffic
>> (UDP/IPv4 in this case,
>> but doesn't seem to matter).
>> Stop traffic, then attempt to create additional 802.1q vlans on the same
>> physical interfaces.
>> The crash only appears to happen after having sent traffic on the
>> interface.
>>
>> Likely it will also crash if one system is sending to another, but so
>> far we've
>> just tested sending-to-self.
>>
>> This appears very reproducible for us, and appears to be the same
>> problem that
>> I had reported against our hacked kernel here:
>>
>> http://www.spinics.net/lists/netdev/msg144748.html
>
> Bleh, I think I see the problem.
>
> If a NIC is in promis mode, it can receive VLAN packets for which there
> are no VLAN devices.
>
> static gro_result_t
> vlan_gro_common(struct napi_struct *napi, struct vlan_group *grp,
> unsigned int vlan_tci, struct sk_buff *skb)
> {
> struct sk_buff *p;
> struct net_device *vlan_dev;
> u16 vlan_id;
>
> if (skb_bond_should_drop(skb, ACCESS_ONCE(skb->dev->master)))
> skb->deliver_no_wcard = 1;
>
> skb->skb_iif = skb->dev->ifindex;
> __vlan_hwaccel_put_tag(skb, vlan_tci);
> vlan_id = vlan_tci & VLAN_VID_MASK;
> vlan_dev = vlan_group_get_device(grp, vlan_id);
>
> if (vlan_dev)
> skb->dev = vlan_dev;
> else if (vlan_id) {
> if (!(skb->dev->flags & IFF_PROMISC))
> goto drop;
> skb->pkt_type = PACKET_OTHERHOST;
> }
>
> You hit that else branch, and then skb->dev remains the physical
> device.
>
> Later, it's passed to:
>
> int vlan_hwaccel_do_receive(struct sk_buff *skb)
> {
> struct net_device *dev = skb->dev;
> struct vlan_rx_stats *rx_stats;
>
> skb->dev = vlan_dev_info(dev)->real_dev;
> netif_nit_deliver(skb);
>
Looks like this should be fixed on net-next,
bool vlan_hwaccel_do_receive(struct sk_buff **skbp)
{
struct sk_buff *skb = *skbp;
u16 vlan_id = skb->vlan_tci & VLAN_VID_MASK;
struct net_device *vlan_dev;
struct vlan_rx_stats *rx_stats;
vlan_dev = vlan_find_dev(skb->dev, vlan_id);
if (!vlan_dev) {
if (vlan_id)
skb->pkt_type = PACKET_OTHERHOST;
return false;
}
If the vlan_dev is not found do not set skb->dev and return false then
in __netif_receive_skb,
if (vlan_tx_tag_present(skb)) {
if (pt_prev) {
ret = deliver_skb(skb, pt_prev, orig_dev);
pt_prev = NULL;
}
if (vlan_hwaccel_do_receive(&skb)) {
ret = __netif_receive_skb(skb);
goto out;
} else if (unlikely(!skb))
goto out;
}
>
> which does no checking before assuming that skb->dev is a vlan
> device.
>
> Things go downhill rapidly after that.
>
>
> Maybe this code in dev.c should check that skb->dev is
> VLAN device before passing to the hwaccel code?
>
> static int __netif_receive_skb(struct sk_buff *skb)
> {
> struct packet_type *ptype, *pt_prev;
> rx_handler_func_t *rx_handler;
> struct net_device *orig_dev;
> struct net_device *master;
> struct net_device *null_or_orig;
> struct net_device *orig_or_bond;
> int ret = NET_RX_DROP;
> __be16 type;
>
> if (!netdev_tstamp_prequeue)
> net_timestamp_check(skb);
>
> if (vlan_tx_tag_present(skb) && vlan_hwaccel_do_receive(skb))
> return NET_RX_SUCCESS;
>
>
> Thanks,
> Ben
>
next prev parent reply other threads:[~2010-10-25 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 17:57 Reproducible VLAN/e1000e crash in 2.6.36 vanilla Ben Greear
2010-10-25 21:18 ` Ben Greear
2010-10-25 21:34 ` John Fastabend [this message]
2010-10-25 21:38 ` Eric Dumazet
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=4CC5F7EB.7010307@intel.com \
--to=john.r.fastabend@intel.com \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).