[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221107202413.7de06ad1@kernel.org>
Date: Mon, 7 Nov 2022 20:24:13 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Saeed Mahameed <saeed@...nel.org>
Cc: "David S. Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Eric Dumazet <edumazet@...gle.com>,
Saeed Mahameed <saeedm@...dia.com>, netdev@...r.kernel.org,
Tariq Toukan <tariqt@...dia.com>,
Moshe Shemesh <moshe@...dia.com>
Subject: Re: [V2 net 05/11] net/mlx5: Fix possible deadlock on
mlx5e_tx_timeout_work
On Sat, 5 Nov 2022 00:10:22 -0700 Saeed Mahameed wrote:
> + /* Once deactivated, new tx_timeout_work won't be initiated. */
> + if (current_work() != &priv->tx_timeout_work)
> + cancel_work_sync(&priv->tx_timeout_work);
The work takes rtnl_lock, are there no callers of
mlx5e_switch_priv_channels() that are under rtnl_lock()?
This patch is definitely going onto my "expecting Fixes"
bingo card :S
Powered by blists - more mailing lists