[PATCH net v2] net: thunderx: avoid direct MTU assignment after WRITE_ONCE()
Simon Horman
horms at kernel.org
Mon Jun 30 04:18:36 PDT 2025
On Sat, Jun 28, 2025 at 10:15:37PM -0700, Alok Tiwari wrote:
...
> @@ -1589,16 +1588,18 @@ static int nicvf_change_mtu(struct net_device *netdev, int new_mtu)
> return -EINVAL;
> }
>
> - WRITE_ONCE(netdev->mtu, new_mtu);
>
> - if (!netif_running(netdev))
> + if (!netif_running(netdev)) {
> + WRITE_ONCE(netdev->mtu, new_mtu);
> return 0;
> + }
>
> if (nicvf_update_hw_max_frs(nic, new_mtu)) {
> - netdev->mtu = orig_mtu;
> return -EINVAL;
> }
nit: curly brackets should be removed here, but see further comment below.
>
> + WRITE_ONCE(netdev->mtu, new_mtu);
> +
> return 0;
> }
Could this be more succinctly expressed as follows?
(Completely untested!)
if (netif_running(netdev) && nicvf_update_hw_max_frs(nic, new_mtu))
return -ENIVAL;
WRITE_ONCE(netdev->mtu, new_mtu);
return 0;
More information about the linux-arm-kernel
mailing list