From: patchwork-bot+netdevbpf@kernel•org
To: Sabrina Dubroca <sd@queasysnail•net>
Cc: netdev@vger•kernel.org, leonro@nvidia•com, atenart@kernel•org,
mstarovoitov@marvell•com, irusskikh@marvell•com
Subject: Re: [PATCH net v3 0/5] macsec: offload-related fixes
Date: Fri, 04 Nov 2022 10:50:17 +0000 [thread overview]
Message-ID: <166755901730.6249.17723300193454709704.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1667204360.git.sd@queasysnail.net>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft•net>:
On Wed, 2 Nov 2022 22:33:11 +0100 you wrote:
> I'm working on a dummy offload for macsec on netdevsim. It just has a
> small SecY and RXSC table so I can trigger failures easily on the
> ndo_* side. It has exposed a couple of issues.
>
> The first patch is a revert of commit c850240b6c41 ("net: macsec:
> report real_dev features when HW offloading is enabled"). That commit
> tried to improve the performance of macsec offload by taking advantage
> of some of the NIC's features, but in doing so, broke macsec offload
> when the lower device supports both macsec and ipsec offload, as the
> ipsec offload feature flags were copied from the real device. Since
> the macsec device doesn't provide xdo_* ops, the XFRM core rejects the
> registration of the new macsec device in xfrm_api_check.
>
> [...]
Here is the summary with links:
- [net,v3,1/5] Revert "net: macsec: report real_dev features when HW offloading is enabled"
https://git.kernel.org/netdev/net/c/8bcd560ae878
- [net,v3,2/5] macsec: delete new rxsc when offload fails
https://git.kernel.org/netdev/net/c/93a30947821c
- [net,v3,3/5] macsec: fix secy->n_rx_sc accounting
https://git.kernel.org/netdev/net/c/73a4b31c9d11
- [net,v3,4/5] macsec: fix detection of RXSCs when toggling offloading
https://git.kernel.org/netdev/net/c/80df4706357a
- [net,v3,5/5] macsec: clear encryption keys from the stack after setting up offload
https://git.kernel.org/netdev/net/c/aaab73f8fba4
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-11-04 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 21:33 [PATCH net v3 0/5] macsec: offload-related fixes Sabrina Dubroca
2022-11-02 21:33 ` [PATCH net v3 1/5] Revert "net: macsec: report real_dev features when HW offloading is enabled" Sabrina Dubroca
2022-11-02 21:33 ` [PATCH net v3 2/5] macsec: delete new rxsc when offload fails Sabrina Dubroca
2022-11-02 21:33 ` [PATCH net v3 3/5] macsec: fix secy->n_rx_sc accounting Sabrina Dubroca
2022-11-02 21:33 ` [PATCH net v3 4/5] macsec: fix detection of RXSCs when toggling offloading Sabrina Dubroca
2022-11-02 21:33 ` [PATCH net v3 5/5] macsec: clear encryption keys from the stack after setting up offload Sabrina Dubroca
2022-11-04 10:50 ` 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=166755901730.6249.17723300193454709704.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=atenart@kernel$(echo .)org \
--cc=irusskikh@marvell$(echo .)com \
--cc=leonro@nvidia$(echo .)com \
--cc=mstarovoitov@marvell$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sd@queasysnail$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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