From: Antoine Tenart <atenart@kernel.org>
To: Sabrina Dubroca <sd@queasysnail.net>, netdev@vger.kernel.org
Cc: Leon Romanovsky <leon@kernel.org>,
Sabrina Dubroca <sd@queasysnail.net>,
Mark Starovoytov <mstarovoitov@marvell.com>,
Igor Russkikh <irusskikh@marvell.com>
Subject: Re: [PATCH net v2 0/5] macsec: offload-related fixes
Date: Thu, 27 Oct 2022 10:45:00 +0200 [thread overview]
Message-ID: <166686030097.40988.16309190373804586041@kwain> (raw)
In-Reply-To: <cover.1666793468.git.sd@queasysnail.net>
Quoting Sabrina Dubroca (2022-10-26 23:56:22)
> 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.
>
> I'm working on re-adding those feature flags when offload is
> available, but I haven't fully solved that yet. I think it would be
> safer to do that second part in net-next considering how complex
> feature interactions tend to be.
>
> v2:
> - better describe the issue introduced by commit c850240b6c41 (Leon
> Romanovsky)
> - drop unnecessary !! (Leon Romanovsky)
>
> Sabrina Dubroca (5):
> Revert "net: macsec: report real_dev features when HW offloading is
> enabled"
> macsec: delete new rxsc when offload fails
> macsec: fix secy->n_rx_sc accounting
> macsec: fix detection of RXSCs when toggling offloading
> macsec: clear encryption keys from the stack after setting up offload
Series,
Reviewed-by: Antoine Tenart <atenart@kernel.org>
Thanks!
prev parent reply other threads:[~2022-10-27 8:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 21:56 [PATCH net v2 0/5] macsec: offload-related fixes Sabrina Dubroca
2022-10-26 21:56 ` [PATCH net v2 1/5] Revert "net: macsec: report real_dev features when HW offloading is enabled" Sabrina Dubroca
2022-10-30 8:13 ` Leon Romanovsky
2022-10-30 11:54 ` Raed Salem
2022-10-30 15:02 ` Raed Salem
2022-10-26 21:56 ` [PATCH net v2 2/5] macsec: delete new rxsc when offload fails Sabrina Dubroca
2022-10-30 8:13 ` Leon Romanovsky
2022-10-26 21:56 ` [PATCH net v2 3/5] macsec: fix secy->n_rx_sc accounting Sabrina Dubroca
2022-10-27 18:29 ` Jakub Kicinski
2022-10-30 8:14 ` Leon Romanovsky
2022-10-26 21:56 ` [PATCH net v2 4/5] macsec: fix detection of RXSCs when toggling offloading Sabrina Dubroca
2022-10-30 8:15 ` Leon Romanovsky
2022-10-26 21:56 ` [PATCH net v2 5/5] macsec: clear encryption keys from the stack after setting up offload Sabrina Dubroca
2022-10-30 8:16 ` Leon Romanovsky
2022-10-27 8:45 ` Antoine Tenart [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=166686030097.40988.16309190373804586041@kwain \
--to=atenart@kernel.org \
--cc=irusskikh@marvell.com \
--cc=leon@kernel.org \
--cc=mstarovoitov@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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