From: David Miller <davem@davemloft.net>
To: greearb@candelatech.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net/core: Allow tagged VLAN packets to flow through VETH devices.
Date: Thu, 21 Oct 2010 04:07:17 -0700 (PDT) [thread overview]
Message-ID: <20101021.040717.241928814.davem@davemloft.net> (raw)
In-Reply-To: <1287167705-28583-1-git-send-email-greearb@candelatech.com>
From: Ben Greear <greearb@candelatech.com>
Date: Fri, 15 Oct 2010 11:35:05 -0700
> When there are VLANs on a VETH device, the packets being transmitted
> through the VETH device may be 4 bytes bigger than MTU. A check
> in dev_forward_skb did not take this into account and so dropped
> these packets.
>
> This patch is needed at least as far back as 2.6.34.7 and should
> be considered for -stable.
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
Applied, although a check of the vlan-capable netdev flag
might be appropriate to add.
prev parent reply other threads:[~2010-10-21 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 18:35 [PATCH] net/core: Allow tagged VLAN packets to flow through VETH devices Ben Greear
2010-10-21 11:07 ` David Miller [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=20101021.040717.241928814.davem@davemloft.net \
--to=davem@davemloft.net \
--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).