linux-kernel - Re: [PATCH] dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <174723498418.115803.4603053071326943266.b4-ty@kernel.org>
Date: Wed, 14 May 2025 16:03:04 +0100
From: Vinod Koul <vkoul@...nel.org>
To: dave.jiang@...el.com, vinicius.gomes@...el.com, 
 dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Yi Sun <yi.sun@...el.com>
Cc: anil.s.keshavamurthy@...el.com, gordon.jin@...el.com
Subject: Re: [PATCH] dmaengine: idxd: Check availability of workqueue
 allocated by idxd wq driver before using


On Fri, 09 May 2025 08:03:04 +0800, Yi Sun wrote:
> Running IDXD workloads in a container with the /dev directory mounted can
> trigger a call trace or even a kernel panic when the parent process of the
> container is terminated.
> 
> This issue occurs because, under certain configurations, Docker does not
> properly propagate the mount replica back to the original mount point.
> 
> [...]

Applied, thanks!

[1/1] dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using
      commit: 17502e7d7b7113346296f6758324798d536c31fd

Best regards,
-- 
~Vinod