From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
dchumak@nvidia.com, roid@nvidia.com, mbloch@nvidia.com,
saeedm@nvidia.com
Subject: Re: [net 1/6] net/mlx5: Lag, fix multipath lag activation
Date: Fri, 27 Aug 2021 09:10:10 +0000 [thread overview]
Message-ID: <163005541087.19735.3077952130395559575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210826221810.215968-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Thu, 26 Aug 2021 15:18:05 -0700 you wrote:
> From: Dima Chumak <dchumak@nvidia.com>
>
> When handling FIB_EVENT_ENTRY_REPLACE event for a new multipath route,
> lag activation can be missed if a stale (struct lag_mp)->mfi pointer
> exists, which was associated with an older multipath route that had been
> removed.
>
> [...]
Here is the summary with links:
- [net,1/6] net/mlx5: Lag, fix multipath lag activation
https://git.kernel.org/netdev/net/c/2f8b6161cca5
- [net,2/6] net/mlx5: Remove all auxiliary devices at the unregister event
https://git.kernel.org/netdev/net/c/8e7e2e8ed0e2
- [net,3/6] net/mlx5e: Fix possible use-after-free deleting fdb rule
https://git.kernel.org/netdev/net/c/9a5f9cc794e1
- [net,4/6] net/mlx5: E-Switch, Set vhca id valid flag when creating indir fwd group
https://git.kernel.org/netdev/net/c/ca6891f9b27d
- [net,5/6] net/mlx5e: Use correct eswitch for stack devices with lag
https://git.kernel.org/netdev/net/c/f9d196bd632b
- [net,6/6] net/mlx5: DR, fix a potential use-after-free bug
https://git.kernel.org/netdev/net/c/6cc64770fb38
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-27 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 22:18 [pull request][net 0/6] mlx5 fixes 2021-08-26 Saeed Mahameed
2021-08-26 22:18 ` [net 1/6] net/mlx5: Lag, fix multipath lag activation Saeed Mahameed
2021-08-27 9:10 ` patchwork-bot+netdevbpf [this message]
2021-08-26 22:18 ` [net 2/6] net/mlx5: Remove all auxiliary devices at the unregister event Saeed Mahameed
2021-08-26 22:18 ` [net 3/6] net/mlx5e: Fix possible use-after-free deleting fdb rule Saeed Mahameed
2021-08-26 22:18 ` [net 4/6] net/mlx5: E-Switch, Set vhca id valid flag when creating indir fwd group Saeed Mahameed
2021-08-26 22:18 ` [net 5/6] net/mlx5e: Use correct eswitch for stack devices with lag Saeed Mahameed
2021-08-26 22:18 ` [net 6/6] net/mlx5: DR, fix a potential use-after-free bug Saeed Mahameed
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=163005541087.19735.3077952130395559575.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dchumak@nvidia.com \
--cc=kuba@kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=roid@nvidia.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.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.