From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net 3/3] eet: ena: invoke netif_carrier_off() only after netdev registered Date: Tue, 02 Jan 2018 14:08:04 -0500 (EST) Message-ID: <20180102.140804.982695913961893372.davem@davemloft.net> References: <1514496620-69953-1-git-send-email-netanel@amazon.com> <1514496620-69953-4-git-send-email-netanel@amazon.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, dwmw@amazon.com, zorik@amazon.com, matua@amazon.com, saeedb@amazon.com, msw@amazon.com, aliguori@amazon.com, nafea@amazon.com, evgenys@amazon.com, gtzalik@amazon.com To: netanel@amazon.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:51114 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750800AbeABTIG (ORCPT ); Tue, 2 Jan 2018 14:08:06 -0500 In-Reply-To: <1514496620-69953-4-git-send-email-netanel@amazon.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Date: Thu, 28 Dec 2017 21:30:20 +0000 > From: Netanel Belgazal > > netif_carrier_off() should be called only after register netdev. > Move the function's call after the registration. > > Signed-off-by: Netanel Belgazal > --- > drivers/net/ethernet/amazon/ena/ena_netdev.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/net/ethernet/amazon/ena/ena_netdev.c b/drivers/net/ethernet/amazon/ena/ena_netdev.c > index fbe21a817bd8..ee50c56765a4 100644 > --- a/drivers/net/ethernet/amazon/ena/ena_netdev.c > +++ b/drivers/net/ethernet/amazon/ena/ena_netdev.c > @@ -3276,14 +3276,14 @@ static int ena_probe(struct pci_dev *pdev, const struct pci_device_id *ent) > > memcpy(adapter->netdev->perm_addr, adapter->mac_addr, netdev->addr_len); > > - netif_carrier_off(netdev); > - > rc = register_netdev(netdev); > if (rc) { > dev_err(&pdev->dev, "Cannot register net device\n"); > goto err_rss; > } > > + netif_carrier_off(netdev); > + You cannot invoke this after register_netdev(), asynchronous activity can cause this call to lose information and lose a link up event.