[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CF9D1877D81D214CB0CA0669EFAE020C066A09@CMEXMB1.ad.emulex.com>
Date: Tue, 14 Aug 2012 12:36:12 +0000
From: <Sathya.Perla@...lex.Com>
To: <shchepetkov@...ras.ru>, <yevgenyp@...lanox.co.il>
CC: <davem@...emloft.net>, <amirv@...lanox.com>,
<ogerlitz@...lanox.com>, <alexg@...lanox.com>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<ldv-project@...ras.ru>
Subject: RE: [PATCH 3/5] net/mlx4_en: Call netif_carrier_off() after
register_netdev()
>-----Original Message-----
>From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org] On
>Behalf Of Ilya Shchepetkov
>
>For carrier detection to work properly when binding the driver with a
>cable unplugged, netif_carrier_off() should be called after
>register_netdev(), not before.
>
>Calling netif_carrier_off() before register_netdev() was causing the
>network interface to miss a linkwatch pending event leading to an
>inconsistent state if the link is not up when interface is initialized.
ndo_open() may be called as soon register_netdev() completes...
When netif_carrier_off() is called *after* register_netdev(), isn't there
a possibility of a ndo_open()->netif_carrier_on() call racing this call, causing
incorrect results?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists