From: Sabrina Dubroca <sd@queasysnail.net>
To: "Radu Pirea (NXP OSS)" <radu-nicolae.pirea@oss.nxp.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, richardcochran@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
sebastian.tobuschat@oss.nxp.com
Subject: Re: [PATCH net-next v7 3/7] net: macsec: revert the MAC address if mdo_upd_secy fails
Date: Fri, 20 Oct 2023 15:45:26 +0200 [thread overview]
Message-ID: <ZTKEdvpNl-gwGpk6@hog> (raw)
In-Reply-To: <20231019120209.290480-4-radu-nicolae.pirea@oss.nxp.com>
2023-10-19, 15:02:05 +0300, Radu Pirea (NXP OSS) wrote:
> /* If h/w offloading is available, propagate to the device */
> - if (macsec_is_offloaded(macsec)) {
> + if (offloaded) {
> const struct macsec_ops *ops;
> struct macsec_context ctx;
>
> ops = macsec_get_ops(macsec, &ctx);
> - if (ops) {
> - ctx.secy = &macsec->secy;
> - macsec_offload(ops->mdo_upd_secy, &ctx);
> + if (!ops) {
> + err = -EINVAL;
For consistency with other places where macsec_get_ops fails, this
should probably be -EOPNOTSUPP.
I'm not opposed to this change, but I'm not sure how it's related to
the missing rollback issue. Can you explain that a bit?
> + goto restore_old_addr;
> }
> +
> + ctx.secy = &macsec->secy;
> + err = macsec_offload(ops->mdo_upd_secy, &ctx);
> + if (err)
> + goto restore_old_addr;
> }
>
> return 0;
> +
> +restore_old_addr:
> + if (dev->flags & IFF_UP) {
> + int err;
[This bit confused me quite a bit, seeing the declaration and the
"return err" out of this block]
> + err = macsec_dev_uc_update(dev, old_addr);
> + if (err)
> + return err;
If we can avoid it, we should try to have a rollback path without any
possible failures, otherwise we'll leave things in a broken state (in
this case, telling the user that the MAC address change failed, but
leaving the new address set on the macsec device).
Paolo suggested to postpone the dev_uc_del until after the offload
code, so we'd end up with something like this [completely untested]:
if (dev->flags & IFF_UP) {
err = dev_uc_add(real_dev, addr->sa_data);
if (err < 0)
return err;
}
ether_addr_copy(old_addr, dev->dev_addr);
eth_hw_addr_set(dev, addr->sa_data);
/* If h/w offloading is available, propagate to the device */
if (macsec_is_offloaded(macsec)) {
// ...
}
if (dev->flags & IFF_UP)
dev_uc_del(real_dev, old_addr);
return 0;
restore_old_addr:
if (dev->flags & IFF_UP)
dev_uc_del(real_dev, addr->sa_data);
eth_hw_addr_set(dev, old_addr);
return err;
Install both UC addresses, then remove the one we don't need.
--
Sabrina
next prev parent reply other threads:[~2023-10-20 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 12:02 [PATCH net-next v7 0/7] Add MACsec support for TJA11XX C45 PHYs Radu Pirea (NXP OSS)
2023-10-19 12:02 ` [PATCH net-next v7 1/7] net: macsec: move sci_to_cpu to macsec header Radu Pirea (NXP OSS)
2023-10-19 12:02 ` [PATCH net-next v7 2/7] net: macsec: documentation for macsec_context and macsec_ops Radu Pirea (NXP OSS)
2023-10-19 12:02 ` [PATCH net-next v7 3/7] net: macsec: revert the MAC address if mdo_upd_secy fails Radu Pirea (NXP OSS)
2023-10-20 13:45 ` Sabrina Dubroca [this message]
2023-10-19 12:02 ` [PATCH net-next v7 4/7] net: macsec: introduce mdo_insert_tx_tag Radu Pirea (NXP OSS)
2023-10-19 12:02 ` [PATCH net-next v7 5/7] net: phy: nxp-c45-tja11xx: add MACsec support Radu Pirea (NXP OSS)
2023-10-19 12:02 ` [PATCH net-next v7 6/7] net: phy: nxp-c45-tja11xx: add MACsec statistics Radu Pirea (NXP OSS)
2023-10-19 12:02 ` [PATCH net-next v7 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=ZTKEdvpNl-gwGpk6@hog \
--to=sd@queasysnail.net \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.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=radu-nicolae.pirea@oss.nxp.com \
--cc=richardcochran@gmail.com \
--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