[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190626.091055.2250153974662071717.davem@davemloft.net>
Date: Wed, 26 Jun 2019 09:10:55 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jonathanh@...dia.com
Cc: peppe.cavallaro@...com, alexandre.torgue@...com,
joabreu@...opsys.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-tegra@...r.kernel.org
Subject: Re: [PATCH 1/2] net: stmmac: Fix possible deadlock when disabling
EEE support
From: Jon Hunter <jonathanh@...dia.com>
Date: Wed, 26 Jun 2019 11:23:21 +0100
> When stmmac_eee_init() is called to disable EEE support, then the timer
> for EEE support is stopped and we return from the function. Prior to
> stopping the timer, a mutex was acquired but in this case it is never
> released and so could cause a deadlock. Fix this by releasing the mutex
> prior to returning from stmmax_eee_init() when stopping the EEE timer.
>
> Fixes: 74371272f97f ("net: stmmac: Convert to phylink and remove phylib logic")
> Signed-off-by: Jon Hunter <jonathanh@...dia.com>
When targetting net-next for a set of changes, make this explicit and clear
by saying "[PATCH net-next ...] ..." in your Subject lines in the future.
Applied.
Powered by blists - more mailing lists