From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, f.fainelli@gmail.com, andrew@lunn.ch,
vivien.didelot@gmail.com, olteanv@gmail.com, davem@davemloft.net,
kuba@kernel.org, rafael.richter@gin.de, daniel.klauer@gin.de
Subject: Re: [PATCH net] net: dsa: mv88e6xxx: flush switchdev FDB workqueue before removing VLAN
Date: Mon, 14 Feb 2022 13:40:09 +0000 [thread overview]
Message-ID: <164484600973.23487.8886750074489246883.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220211174506.3874409-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 11 Feb 2022 19:45:06 +0200 you wrote:
> mv88e6xxx is special among DSA drivers in that it requires the VTU to
> contain the VID of the FDB entry it modifies in
> mv88e6xxx_port_db_load_purge(), otherwise it will return -EOPNOTSUPP.
>
> Sometimes due to races this is not always satisfied even if external
> code does everything right (first deletes the FDB entries, then the
> VLAN), because DSA commits to hardware FDB entries asynchronously since
> commit c9eb3e0f8701 ("net: dsa: Add support for learning FDB through
> notification").
>
> [...]
Here is the summary with links:
- [net] net: dsa: mv88e6xxx: flush switchdev FDB workqueue before removing VLAN
https://git.kernel.org/netdev/net/c/a2614140dc0f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-14 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 17:45 [PATCH net] net: dsa: mv88e6xxx: flush switchdev FDB workqueue before removing VLAN Vladimir Oltean
2022-02-14 13:40 ` patchwork-bot+netdevbpf [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=164484600973.23487.8886750074489246883.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=daniel.klauer@gin.de \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=rafael.richter@gin.de \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.