Netdev List
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Frank Wunderlich <frank-w@public-files.de>,
	netdev@vger.kernel.org, andrew@lunn.ch,
	Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: [BUG] [FIX] net: dsa: oops in br_vlan_enabled
Date: Sun, 17 Feb 2019 14:38:27 -0800	[thread overview]
Message-ID: <38b4f192-7641-8d22-4691-0c5f994f3c55@gmail.com> (raw)
In-Reply-To: <trinity-1108d2b6-42f0-4770-b561-6a66804f210a-1550430319767@3c-app-gmx-bs61>



On 2/17/2019 11:05 AM, Frank Wunderlich wrote:
> Hi Florian
> 
> a user from Bananapi-forum has reported the oops and i had reproduced this and patched out this oops.
> That means not that vlan in bridge works, only no crash.
> 
> my kernel only conatins the second gmac dsa-patches for mt7530/bpi-r2 i've posted at the end of last year, but the oops also occur without them.
> 
> have not changed bridge vlan-configuration by
> 
> echo 1 > /sys/class/net/bridge_name/bridge/vlan_filtering
> 
> maybe that vlan-objects/configuration is not passed through, but there should happen no oops.
> 
> kernel-source is here: https://github.com/frank-w/BPI-R2-4.14/tree/4.19-main
> 
> ps: please take me in CC so i can answer directly

You were in the To: of my previous reply, let's move it back there since
it has all context.
-- 
Florian

  reply	other threads:[~2019-02-17 22:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 19:05 Re: [BUG] [FIX] net: dsa: oops in br_vlan_enabled Frank Wunderlich
2019-02-17 22:38 ` Florian Fainelli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-16 16:22 Frank Wunderlich
2019-02-17 17:13 ` Florian Fainelli
2019-02-17 23:20   ` Florian Fainelli
2019-02-18 17:11     ` Aw: " Frank Wunderlich
2019-02-18 19:09       ` Florian Fainelli

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=38b4f192-7641-8d22-4691-0c5f994f3c55@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=frank-w@public-files.de \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@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