From: David Miller <davem@davemloft.net>
To: balbi@ti.com
Cc: netdev@vger.kernel.org, linux-omap@vger.kernel.org,
stable@vger.kernel.org, mugunthanvnm@ti.com
Subject: Re: [PATCH] net: ethernet: cpsw: ignore VLAN ID 1
Date: Tue, 06 Jan 2015 14:13:23 -0500 (EST) [thread overview]
Message-ID: <20150106.141323.2091288413667564444.davem@davemloft.net> (raw)
In-Reply-To: <1420566212-30081-1-git-send-email-balbi@ti.com>
From: Felipe Balbi <balbi@ti.com>
Date: Tue, 6 Jan 2015 11:43:32 -0600
> CPSW completely hangs if we add, and later remove,
> VLAN ID #1. What happens is that after removing
> VLAN ID #1, no packets will be received by CPSW
> rendering network unusable.
>
> In order to "fix" the issue, we're returning -EINVAL
> if anybody tries to add VLAN ID #1. While at that,
> also filter out any ID > 4095 because we only have
> 12 bits for VLAN IDs.
>
> Fixes: 3b72c2f (drivers: net:ethernet: cpsw: add support for VLAN)
> Cc: <stable@vger.kernel.org> # v3.9+
> Cc: Mugunthan V N <mugunthanvnm@ti.com>
> Tested-by: Schuyler Patton <spatton@ti.com>
> Signed-off-by: Felipe Balbi <balbi@ti.com>
You can't just unilaterally make one VLAN ID unusable.
A better way to handle this situation must be found,
and if that means turning off hw VLAN support completely,
that's a much better alternative to this.
I'm not applying this patch, sorry.
next prev parent reply other threads:[~2015-01-06 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 17:43 [PATCH] net: ethernet: cpsw: ignore VLAN ID 1 Felipe Balbi
2015-01-06 19:13 ` David Miller [this message]
2015-01-06 20:31 ` Felipe Balbi
2015-01-06 21:59 ` David Miller
2015-01-06 22:04 ` Felipe Balbi
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=20150106.141323.2091288413667564444.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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).