From: Simon Horman Date: Wed, 16 Aug 2017 07:37:44 +0000 (+0200) Subject: nfp: process MTU updates from firmware flower app X-Git-Tag: v4.14-rc1~130^2~232^2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2dff1962242111cc4517119f690587b87573ffc5;p=platform%2Fkernel%2Flinux-rpi.git nfp: process MTU updates from firmware flower app Now that control message processing occurs in a workqueue rather than a BH handler MTU updates received from the firmware may be safely processed. Signed-off-by: Simon Horman Reviewed-by: Jakub Kicinski Signed-off-by: David S. Miller --- diff --git a/drivers/net/ethernet/netronome/nfp/flower/cmsg.c b/drivers/net/ethernet/netronome/nfp/flower/cmsg.c index 6c8c224..806924b 100644 --- a/drivers/net/ethernet/netronome/nfp/flower/cmsg.c +++ b/drivers/net/ethernet/netronome/nfp/flower/cmsg.c @@ -150,10 +150,17 @@ nfp_flower_cmsg_portmod_rx(struct nfp_app *app, struct sk_buff *skb) return; } - if (link) + if (link) { + u16 mtu = be16_to_cpu(msg->mtu); + netif_carrier_on(netdev); - else + + /* An MTU of 0 from the firmware should be ignored */ + if (mtu) + dev_set_mtu(netdev, mtu); + } else { netif_carrier_off(netdev); + } rcu_read_unlock(); }