From: Eric Dumazet <eric.dumazet@gmail.com>
To: roy.qing.li@gmail.com
Cc: netdev@vger.kernel.org, Pravin B Shelar <pshelar@nicira.com>
Subject: Re: [PATCH net-next] net/core: move vlan_depth out of while loop in skb_network_protocol()
Date: Tue, 12 Mar 2013 07:56:26 +0100 [thread overview]
Message-ID: <1363071386.13690.7.camel@edumazet-glaptop> (raw)
In-Reply-To: <1363069844-10624-1-git-send-email-roy.qing.li@gmail.com>
On Tue, 2013-03-12 at 14:30 +0800, roy.qing.li@gmail.com wrote:
> From: Li RongQing <roy.qing.li@gmail.com>
>
> move vlan_depth out of while loop, or else vlan_depth always is ETH_HLEN,
> can not be increased, and lead to infinite loop when frame has two vlan headers.
>
> Signed-off-by: Li RongQing <roy.qing.li@gmail.com>
> ---
> net/core/dev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/core/dev.c b/net/core/dev.c
> index 90cee5b..35a6a6e 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -2211,9 +2211,9 @@ EXPORT_SYMBOL(skb_checksum_help);
> __be16 skb_network_protocol(struct sk_buff *skb)
> {
> __be16 type = skb->protocol;
> + int vlan_depth = ETH_HLEN;
>
> while (type == htons(ETH_P_8021Q)) {
> - int vlan_depth = ETH_HLEN;
> struct vlan_hdr *vh;
>
> if (unlikely(!pskb_may_pull(skb, vlan_depth + VLAN_HLEN)))
Nice catch, bug added in commit 05e8ef4ab2d8087d (net: factor out
skb_mac_gso_segment() from skb_gso_segment() )
So this is a patch for net tree, not for net-next.
Acked-by: Eric Dumazet <edumazet@google.com>
next prev parent reply other threads:[~2013-03-12 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 6:30 [PATCH net-next] net/core: move vlan_depth out of while loop in skb_network_protocol() roy.qing.li
2013-03-12 6:56 ` Eric Dumazet [this message]
2013-03-12 15:47 ` David Miller
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=1363071386.13690.7.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=roy.qing.li@gmail.com \
/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