On Wed, Jun 15, 2022 at 02:01:54PM +0800, zhichaox.z...@intel.com wrote:
> From: Zhichao Zeng
>
> The eal-intr-thread is not closed before memory cleanup in the
> process of exiting. There is a small probability that when the
> eal-intr-thread is about to use some pointers, the memory were
> just
.@redhat.com; step...@networkplumber.org;
> m...@smartsharesystems.com; Zeng, ZhichaoX ;
> Richardson, Bruce > ; Harman Kalra
>
> Subject: [PATCH v4] lib/eal: fix segfaults due to thread exit order
>
> From: Zhichao Zeng
>
> The eal-intr-thread is not closed before memor
On Fri, Jun 24, 2022 at 3:42 AM Zeng, ZhichaoX wrote:
>
> Hi David, Harman
> Please review this patch at your convenience, it's been about a month
> since the v1 version.
> Thanks!
Yes, it's been a month.
Feel free to help on reviewing patches from others so that reviews can
be quicker f
dk.org; Yang, Qiming ;
> david.march...@redhat.com; step...@networkplumber.org;
> m...@smartsharesystems.com; Zeng, ZhichaoX ;
> Richardson, Bruce > ; Harman Kalra
>
> Subject: [PATCH v4] lib/eal: fix segfaults due to thread exit order
>
> From: Zhichao Zeng
>
&g
From: Zhichao Zeng
The eal-intr-thread is not closed before memory cleanup in the
process of exiting. There is a small probability that when the
eal-intr-thread is about to use some pointers, the memory were
just cleaned, which cause the segment fault error caught by ASan.
This patch close the e
5 matches
Mail list logo
