From: "Radu Pirea (OSS)" <radu-nicolae.pirea@oss.nxp.com>
To: Igor Russkikh <irusskikh@marvell.com>,
Sabrina Dubroca <sd@queasysnail.net>,
Dmitry Bezrukov <dbezrukov@marvell.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, richardcochran@gmail.com,
sebastian.tobuschat@oss.nxp.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [EXT] Re: [PATCH net-next v5 3/7] net: macsec: indicate next pn update when offloading
Date: Wed, 27 Sep 2023 15:33:02 +0300 [thread overview]
Message-ID: <9098b8dd-65d4-b629-d6ab-6e2fdd041148@oss.nxp.com> (raw)
In-Reply-To: <f8d79f01-38d6-9385-f213-b34779b8bb54@marvell.com>
On 26.09.2023 15:16, Igor Russkikh wrote:
> Hi guys,
>
>> On 21.09.2023 18:11, Sabrina Dubroca wrote:
>>> 2023-09-20, 12:22:33 +0300, Radu Pirea (NXP OSS) wrote:
>>>> Indicate next PN update using update_pn flag in macsec_context.
>>>> Offloaded MACsec implementations does not know whether or not the
>>>> MACSEC_SA_ATTR_PN attribute was passed for an SA update and assume
>>>> that next PN should always updated, but this is not always true.
>>>
>>> This should probably go through net so that we can fix some drivers
>>> that are currently doing the wrong thing. octeontx2 should be
>>> fixable. atlantic looks like it would reset the PN to whatever was
>>> read during the last dump, and it's unclear if that can be fixed
>>> (AFAIU set_egress_sa_record writes the whole config at once). mscc
>
> Thats correct, atlantic hardware requires full table to be in data buffer registers.
> I really doubt its possible to skip PN writing.
>
>>> doesn't seem to modify the PN (even if requested -- should it should
>>> reject the update), and mlx5 doesn't allow PN update (by storing the
>>> initial value of next_pn on SA creation).
>>
>> I updated octeontx2, mssc and mlx5. Atlantic is unclear.
>>
>> Mark, Igor, in the atlantic MACsec driver, can the SAs be updated
>> without a PN update?
>
> Reviewed the code and the docs I have - my view is it can not.
> All the packed record in macsec_api.c:set_egress_sa_record is expected by hardware in full.
Ok. I will not touch atlantic.
--
Radu P.
next prev parent reply other threads:[~2023-09-27 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 9:22 [PATCH net-next v5 0/7] Add MACsec support for TJA11XX C45 PHYs Radu Pirea (NXP OSS)
2023-09-20 9:22 ` [PATCH net-next v5 1/7] net: macsec: move sci_to_cpu to macsec header Radu Pirea (NXP OSS)
2023-09-20 9:22 ` [PATCH net-next v5 2/7] net: macsec: documentation for macsec_context and macsec_ops Radu Pirea (NXP OSS)
2023-09-20 9:22 ` [PATCH net-next v5 3/7] net: macsec: indicate next pn update when offloading Radu Pirea (NXP OSS)
2023-09-21 15:11 ` Sabrina Dubroca
2023-09-22 15:54 ` Radu Pirea (OSS)
2023-09-26 12:16 ` [EXT] " Igor Russkikh
2023-09-27 12:33 ` Radu Pirea (OSS) [this message]
2023-09-20 9:22 ` [PATCH net-next v5 4/7] net: macsec: introduce mdo_insert_tx_tag Radu Pirea (NXP OSS)
2023-09-20 9:22 ` [PATCH net-next v5 5/7] net: phy: nxp-c45-tja11xx: add MACsec support Radu Pirea (NXP OSS)
2023-09-20 9:22 ` [PATCH net-next v5 6/7] net: phy: nxp-c45-tja11xx: add MACsec statistics Radu Pirea (NXP OSS)
2023-09-20 9:22 ` [PATCH net-next v5 7/7] net: phy: nxp-c45-tja11xx: implement mdo_insert_tx_tag Radu Pirea (NXP OSS)
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=9098b8dd-65d4-b629-d6ab-6e2fdd041148@oss.nxp.com \
--to=radu-nicolae.pirea@oss.nxp.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dbezrukov@marvell.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=sd@queasysnail.net \
--cc=sebastian.tobuschat@oss.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®