[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 2/2] xen/pvcalls: destroy the per-socket workqueue on release

To: sstabellini@xxxxxxxxxx
From: Yehyeong Lee <yhlee@xxxxxxxxxxxxxxxxxx>
Date: Tue, 10 Nov 2026 21:55:08 +0900
Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=20260707 header.d=isslab-korea-ac-kr.20260707.gappssmtp.com header.i="@isslab-korea-ac-kr.20260707.gappssmtp.com" header.h="Content-Transfer-Encoding:MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From"
Cc: jgross@xxxxxxxx, oleksandr_tyshchenko@xxxxxxxx, boris.ostrovsky@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, stable@xxxxxxxxxxxxxxx
Delivery-date: Tue, 10 Nov 2026 13:14:28 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Mon, 9 Nov 2026, Stefano Stabellini wrote:
> Please move the call to destroy_workqueue() just after flush_work().

Done in v2:
https://lore.kernel.org/all/20261110125002.46683-1-yhlee@xxxxxxxxxxxxxxxxxx/

Best regards,
Yehyeong Lee

References:
- [PATCH 0/2] xen/pvcalls: fix the backend error path and a workqueue leak
  - From: Yehyeong Lee
- [PATCH 2/2] xen/pvcalls: destroy the per-socket workqueue on release
  - From: Yehyeong Lee
- Re: [PATCH 2/2] xen/pvcalls: destroy the per-socket workqueue on release
  - From: Stefano Stabellini

Prev by Date: Re: [RFC PATCH 2/2] misra: deviate R2.6 for the labels generated by CASE_SIMD_*
Next by Date: Re: [PATCH v5 4/4] x86: prefer shadow stack for producing call traces
Previous by thread: Re: [PATCH 2/2] xen/pvcalls: destroy the per-socket workqueue on release
Next by thread: [PATCH 1/2] xen/pvcalls: unwind pvcalls_new_active_socket() step by step
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.