> -Original Message-
> From: Doherty, Declan
> Sent: Thursday, March 30, 2017 12:45 PM
> To: Gonzalez Monroy, Sergio; dev@dpdk.org
> Cc: De Lara Guarch, Pablo; sta...@dpdk.org
> Subject: Re: [PATCH] crypto/aesni_gcm: do crypto op in dequeue function
>
> On 29/03/17 14:42, Sergio Gonzalez
-Original Message-
From: De Lara Guarch, Pablo
Sent: Thursday, March 30, 2017 12:54 PM
To: Doherty, Declan ; Gonzalez Monroy, Sergio
; dev@dpdk.org
Cc: sta...@dpdk.org
Subject: RE: [PATCH] crypto/aesni_gcm: do crypto op in dequeue function
> -Original Message-
> From: Doherty
> -Original Message-
> From: Doherty, Declan
> Sent: Thursday, March 30, 2017 12:45 PM
> To: Gonzalez Monroy, Sergio; dev@dpdk.org
> Cc: De Lara Guarch, Pablo; sta...@dpdk.org
> Subject: Re: [PATCH] crypto/aesni_gcm: do crypto op in dequeue function
>
> On 29/03/17 14:42, Sergio Gonzalez
On 29/03/17 14:42, Sergio Gonzalez Monroy wrote:
There is bug when more crypto ops are enqueued than dequeued.
The return value is not checked when trying to enqueue the
processed crypto op into the internal ring, which in the case of being
full will results in crypto ops and mbufs being leaked.
There is bug when more crypto ops are enqueued than dequeued.
The return value is not checked when trying to enqueue the
processed crypto op into the internal ring, which in the case of being
full will results in crypto ops and mbufs being leaked.
The issue is more obvious with different cores doin
5 matches
Mail list logo
