[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <42269a37-0353-29c8-ce13-51cb2feeb9af@gmail.com>
Date: Thu, 18 Jul 2019 10:23:46 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Benjamin Poirier <bpoirier@...e.com>,
David Miller <davem@...emloft.net>
Cc: Sathya Perla <sathya.perla@...adcom.com>,
Ajit Khaparde <ajit.khaparde@...adcom.com>,
Sriharsha Basavapatna <sriharsha.basavapatna@...adcom.com>,
Somnath Kotur <somnath.kotur@...adcom.com>,
Firo Yang <fyang@...e.com>,
Saeed Mahameed <saeedm@...lanox.com>, netdev@...r.kernel.org
Subject: Re: [PATCH net] be2net: Synchronize be_update_queues with
dev_watchdog
On 7/17/19 6:42 PM, Benjamin Poirier wrote:
> As pointed out by Firo Yang, a netdev tx timeout may trigger just before an
> ethtool set_channels operation is started. be_tx_timeout(), which dumps
> some queue structures, is not written to run concurrently with
> be_update_queues(), which frees/allocates those queues structures. Add some
> synchronization between the two.
>
> Message-id: <CH2PR18MB31898E033896F9760D36BFF288C90@...PR18MB3189.namprd18.prod.outlook.com>
> Signed-off-by: Benjamin Poirier <bpoirier@...e.com>
Would not moving the netif_tx_disable() in be_close() further up in the
function resolve that problem as well?
--
Florian
Powered by blists - more mailing lists