From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: syzbot+9ba1174359adba5a5b7c@syzkaller.appspotmail.com,
jiri@resnulli.us, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org,
syzkaller-bugs@googlegroups.com, idosch@idosch.org,
nikolay@nvidia.com, roopa@nvidia.com, kuba@kernel.org,
davem@davemloft.net
Subject: Re: [Bridge] [PATCH net] net: bridge: validate the NUD_PERMANENT bit when adding an extern_learn FDB entry
Date: Mon, 02 Aug 2021 22:10:05 +0000 [thread overview]
Message-ID: <162794220536.7989.3987115619010185604.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210801231730.7493-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Mon, 2 Aug 2021 02:17:30 +0300 you wrote:
> Currently it is possible to add broken extern_learn FDB entries to the
> bridge in two ways:
>
> 1. Entries pointing towards the bridge device that are not local/permanent:
>
> ip link add br0 type bridge
> bridge fdb add 00:01:02:03:04:05 dev br0 self extern_learn static
>
> [...]
Here is the summary with links:
- [net] net: bridge: validate the NUD_PERMANENT bit when adding an extern_learn FDB entry
https://git.kernel.org/netdev/net/c/0541a6293298
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
jiri@resnulli.us, idosch@idosch.org, roopa@nvidia.com,
nikolay@nvidia.com, bridge@lists.linux-foundation.org,
syzkaller-bugs@googlegroups.com,
syzbot+9ba1174359adba5a5b7c@syzkaller.appspotmail.com
Subject: Re: [PATCH net] net: bridge: validate the NUD_PERMANENT bit when adding an extern_learn FDB entry
Date: Mon, 02 Aug 2021 22:10:05 +0000 [thread overview]
Message-ID: <162794220536.7989.3987115619010185604.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210801231730.7493-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Mon, 2 Aug 2021 02:17:30 +0300 you wrote:
> Currently it is possible to add broken extern_learn FDB entries to the
> bridge in two ways:
>
> 1. Entries pointing towards the bridge device that are not local/permanent:
>
> ip link add br0 type bridge
> bridge fdb add 00:01:02:03:04:05 dev br0 self extern_learn static
>
> [...]
Here is the summary with links:
- [net] net: bridge: validate the NUD_PERMANENT bit when adding an extern_learn FDB entry
https://git.kernel.org/netdev/net/c/0541a6293298
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-08-02 22:10 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 23:17 [Bridge] [PATCH net] net: bridge: validate the NUD_PERMANENT bit when adding an extern_learn FDB entry Vladimir Oltean
2021-08-01 23:17 ` Vladimir Oltean
2021-08-02 7:42 ` [Bridge] " Nikolay Aleksandrov
2021-08-02 7:42 ` Nikolay Aleksandrov
2021-08-02 9:20 ` [Bridge] " Vladimir Oltean
2021-08-02 9:20 ` Vladimir Oltean
2021-08-02 9:42 ` [Bridge] " Nikolay Aleksandrov
2021-08-02 9:42 ` Nikolay Aleksandrov
2021-08-02 10:52 ` [Bridge] " Vladimir Oltean
2021-08-02 10:52 ` Vladimir Oltean
2021-08-02 11:02 ` [Bridge] " Nikolay Aleksandrov
2021-08-02 11:02 ` Nikolay Aleksandrov
2021-08-02 11:20 ` [Bridge] " Vladimir Oltean
2021-08-02 11:20 ` Vladimir Oltean
2021-08-02 11:25 ` [Bridge] " Nikolay Aleksandrov
2021-08-02 11:25 ` Nikolay Aleksandrov
2021-08-02 22:10 ` patchwork-bot+netdevbpf [this message]
2021-08-02 22:10 ` patchwork-bot+netdevbpf
2021-08-09 12:16 ` [Bridge] " Ido Schimmel
2021-08-09 12:16 ` Ido Schimmel
2021-08-09 12:32 ` [Bridge] " Vladimir Oltean
2021-08-09 12:32 ` Vladimir Oltean
2021-08-09 15:33 ` [Bridge] " Nikolay Aleksandrov
2021-08-09 15:33 ` Nikolay Aleksandrov
2021-08-10 6:40 ` [Bridge] " Ido Schimmel
2021-08-10 6:40 ` Ido Schimmel
2021-08-10 7:21 ` [Bridge] [PATCH net] net: bridge: fix flags interpretation for extern learn fdb entries Nikolay Aleksandrov
2021-08-10 7:21 ` Nikolay Aleksandrov
2021-08-10 11:00 ` [Bridge] [PATCH net v2] " Nikolay Aleksandrov
2021-08-10 11:00 ` Nikolay Aleksandrov
2021-08-10 13:50 ` [Bridge] " Vladimir Oltean
2021-08-10 13:50 ` Vladimir Oltean
2021-08-10 20:20 ` [Bridge] " patchwork-bot+netdevbpf
2021-08-10 20:20 ` patchwork-bot+netdevbpf
2021-08-09 16:05 ` [Bridge] [PATCH net] net: bridge: validate the NUD_PERMANENT bit when adding an extern_learn FDB entry Vladimir Oltean
2021-08-09 16:05 ` Vladimir Oltean
2021-08-10 6:46 ` [Bridge] " Ido Schimmel
2021-08-10 6:46 ` Ido Schimmel
2021-08-10 10:09 ` [Bridge] " Vladimir Oltean
2021-08-10 10:09 ` Vladimir Oltean
2021-08-10 10:15 ` [Bridge] " Nikolay Aleksandrov
2021-08-10 10:15 ` Nikolay Aleksandrov
2021-08-10 10:38 ` [Bridge] " Vladimir Oltean
2021-08-10 10:38 ` Vladimir Oltean
2021-08-10 10:43 ` [Bridge] " Nikolay Aleksandrov
2021-08-10 10:43 ` Nikolay Aleksandrov
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=162794220536.7989.3987115619010185604.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=roopa@nvidia.com \
--cc=syzbot+9ba1174359adba5a5b7c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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.