Hi Gabe,
> -Original Message-
> From: Carrillo, Erik G
> Sent: Thursday, August 11, 2022 1:00 AM
> To: Naga Harish K, S V
> Cc: dev@dpdk.org; sta...@dpdk.org
> Subject: RE: [PATCH v2 3/4] timer: fix function to stop all timers
>
> Hi Harish,
>
> > --
On Wed, 10 Aug 2022 19:29:36 +
"Carrillo, Erik G" wrote:
> Hi Harish,
>
> > -Original Message-
> > From: Naga Harish K, S V
> > Sent: Wednesday, August 10, 2022 2:10 AM
> > To: Carrillo, Erik G
> > Cc: dev@dpdk.org; sta...@dpdk.org
&
Hi Harish,
> -Original Message-
> From: Naga Harish K, S V
> Sent: Wednesday, August 10, 2022 2:10 AM
> To: Carrillo, Erik G
> Cc: dev@dpdk.org; sta...@dpdk.org
> Subject: [PATCH v2 3/4] timer: fix function to stop all timers
>
> There is a possibility of deadl
There is a possibility of deadlock in this API,
as same spinlock is tried to be acquired in nested manner.
In timer_del function, if the previous owner and current owner lcore
are different, the lock is tried to be acquired even though the same
lock is already acquired by the caller of timer_del f
There is a possibility of deadlock in this API,
as same spinlock is tried to be acquired in nested manner.
In timer_del function, if the previous owner and current owner lcore
are different, the lock is tried to be acquired even though the same
lock is already acquired by the caller of timer_del f
5 matches
Mail list logo
