[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <201408141319.s7EDJl9l031767@thirdoffive.cmf.nrl.navy.mil>
Date: Thu, 14 Aug 2014 09:19:47 -0400
From: Chas Williams - CONTRACTOR <chas@....nrl.navy.mil>
To: netdev@...r.kernel.org, linux-atm-general@...ts.sourceforge.net
Subject: [PATCH net-next] lec: Use rtnl lock/unlock when updating MTU
The LECS response contains the MTU that should be used. Correctly
synchronize with other layers when updating.
Signed-off-by: Chas Williams - CONTRACTOR <chas@....nrl.navy.mil>
---
net/atm/lec.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/net/atm/lec.c b/net/atm/lec.c
index 4c5b8ba..6e13369 100644
--- a/net/atm/lec.c
+++ b/net/atm/lec.c
@@ -410,9 +410,11 @@ static int lec_atm_send(struct atm_vcc *vcc, struct sk_buff *skb)
priv->lane2_ops = NULL;
if (priv->lane_version > 1)
priv->lane2_ops = &lane2_ops;
+ rtnl_lock();
if (dev_set_mtu(dev, mesg->content.config.mtu))
pr_info("%s: change_mtu to %d failed\n",
dev->name, mesg->content.config.mtu);
+ rtnl_unlock();
priv->is_proxy = mesg->content.config.is_proxy;
break;
case l_flush_tran_id:
--
1.9.3
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists