* [dpdk-dev] [PATCH v2] net/axgbe: fix potential unreleased lock problem
@ 2021-08-26 19:02 Chengfeng Ye
2021-09-08 13:39 ` Ferruh Yigit
0 siblings, 1 reply; 2+ messages in thread
From: Chengfeng Ye @ 2021-08-26 19:02 UTC (permalink / raw)
To: asomalap; +Cc: dev, Chengfeng Ye
The lock pdata->phy_mutex may not be correctly released if the
function return in these two branches, which may lead to
deadlock if the lock is acquired again.
Cc: cyeaa@connect.ust.hk
Bugzilla ID: 776
Signed-off-by: Chengfeng Ye <cyeaa@connect.ust.hk>
---
drivers/net/axgbe/axgbe_phy_impl.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/net/axgbe/axgbe_phy_impl.c b/drivers/net/axgbe/axgbe_phy_impl.c
index 02236ec192..cf39095ee4 100644
--- a/drivers/net/axgbe/axgbe_phy_impl.c
+++ b/drivers/net/axgbe/axgbe_phy_impl.c
@@ -418,8 +418,10 @@ static int axgbe_phy_get_comm_ownership(struct axgbe_port *pdata)
*/
pthread_mutex_lock(&pdata->phy_mutex);
- if (phy_data->comm_owned)
+ if (phy_data->comm_owned) {
+ pthread_mutex_unlock(&pdata->phy_mutex);
return 0;
+ }
/* Clear the mutexes */
XP_IOWRITE(pdata, XP_I2C_MUTEX, AXGBE_MUTEX_RELEASE);
@@ -444,6 +446,7 @@ static int axgbe_phy_get_comm_ownership(struct axgbe_port *pdata)
XP_IOWRITE(pdata, XP_MDIO_MUTEX, mutex_id);
phy_data->comm_owned = 1;
+ pthread_mutex_unlock(&pdata->phy_mutex);
return 0;
}
--
2.17.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-dev] [PATCH v2] net/axgbe: fix potential unreleased lock problem
2021-08-26 19:02 [dpdk-dev] [PATCH v2] net/axgbe: fix potential unreleased lock problem Chengfeng Ye
@ 2021-09-08 13:39 ` Ferruh Yigit
0 siblings, 0 replies; 2+ messages in thread
From: Ferruh Yigit @ 2021-09-08 13:39 UTC (permalink / raw)
To: Chengfeng Ye, asomalap; +Cc: dev
On 8/26/2021 8:02 PM, Chengfeng Ye wrote:
> The lock pdata->phy_mutex may not be correctly released if the
> function return in these two branches, which may lead to
> deadlock if the lock is acquired again.
>
> Cc: cyeaa@connect.ust.hk
> Bugzilla ID: 776
>
> Signed-off-by: Chengfeng Ye <cyeaa@connect.ust.hk>
> ---
> drivers/net/axgbe/axgbe_phy_impl.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/axgbe/axgbe_phy_impl.c b/drivers/net/axgbe/axgbe_phy_impl.c
> index 02236ec192..cf39095ee4 100644
> --- a/drivers/net/axgbe/axgbe_phy_impl.c
> +++ b/drivers/net/axgbe/axgbe_phy_impl.c
> @@ -418,8 +418,10 @@ static int axgbe_phy_get_comm_ownership(struct axgbe_port *pdata)
> */
> pthread_mutex_lock(&pdata->phy_mutex);
>
> - if (phy_data->comm_owned)
> + if (phy_data->comm_owned) {
> + pthread_mutex_unlock(&pdata->phy_mutex);
> return 0;
> + }
>
> /* Clear the mutexes */
> XP_IOWRITE(pdata, XP_I2C_MUTEX, AXGBE_MUTEX_RELEASE);
> @@ -444,6 +446,7 @@ static int axgbe_phy_get_comm_ownership(struct axgbe_port *pdata)
> XP_IOWRITE(pdata, XP_MDIO_MUTEX, mutex_id);
>
> phy_data->comm_owned = 1;
> + pthread_mutex_unlock(&pdata->phy_mutex);
> return 0;
> }
>
>
'axgbe_phy_get_comm_ownership()' seems intended to keep the lock on success.
Please also check:
Fixes: c8c2296b5974 ("net/axgbe: fix double unlock")
Perhaps you can comment the 'axgbe_phy_get_comm_ownership()' function instead?
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-09-08 13:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-26 19:02 [dpdk-dev] [PATCH v2] net/axgbe: fix potential unreleased lock problem Chengfeng Ye
2021-09-08 13:39 ` Ferruh Yigit
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).