Re: [dpdk-dev] [PATCH v2] net/axgbe: fix potential unreleased lock problem

2021-09-08 Thread Ferruh Yigit
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: cy...@connect.ust.hk > Bugzilla ID: 776 > > Signed-off-by: Chengfeng Ye > --- >

Re: [dpdk-dev] [PATCH v2] net/axgbe: fix potential unreleased lock problem in axgbe_i2c_xfer

2021-09-08 Thread Ferruh Yigit
On 8/26/2021 7:55 PM, Chengfeng Ye wrote: > The lock pdata->i2c_mutex is not released if the function return in > these two patched branches, which may lead to deadlock problem if > this lock is acquired again. > > Cc: cy...@connect.ust.hk > Bugzilla ID: 777 > > Signed-off-by: Chengfeng Ye Revi

[dpdk-dev] [PATCH v2] net/axgbe: fix potential unreleased lock problem

2021-08-26 Thread 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: cy...@connect.ust.hk Bugzilla ID: 776 Signed-off-by: Chengfeng Ye --- drivers/net/axgbe/axgbe_phy_impl.c | 5 - 1 file changed,

[dpdk-dev] [PATCH v2] net/axgbe: fix potential unreleased lock problem in axgbe_i2c_xfer

2021-08-26 Thread Chengfeng Ye
The lock pdata->i2c_mutex is not released if the function return in these two patched branches, which may lead to deadlock problem if this lock is acquired again. Cc: cy...@connect.ust.hk Bugzilla ID: 777 Signed-off-by: Chengfeng Ye --- drivers/net/axgbe/axgbe_i2c.c | 2 ++ 1 file changed, 2 in