linux-kernel - Re: [PATCH v2] dmaengine: idxd: Check for driver name match before sva user feature

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: <171250793335.435322.3691428203593315560.b4-ty@kernel.org>
Date: Sun, 07 Apr 2024 22:08:53 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Fenghua Yu <fenghua.yu@...el.com>, Dave Jiang <dave.jiang@...el.com>, 
 Jerry Snitselaar <jsnitsel@...hat.com>
Cc: dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] dmaengine: idxd: Check for driver name match before
 sva user feature


On Fri, 05 Apr 2024 14:39:41 -0700, Jerry Snitselaar wrote:
> Currently if the user driver is probed on a workqueue configured for
> another driver with SVA not enabled on the system, it will print
> out a number of probe failing messages like the following:
> 
>     [   264.831140] user: probe of wq13.0 failed with error -95
> 
> On some systems, such as GNR, the number of messages can
> reach over 100.
> 
> [...]

Applied, thanks!

[1/1] dmaengine: idxd: Check for driver name match before sva user feature
      commit: c863062cf8250d8330859fc1d730b2aed3313bcd

Best regards,
-- 
~Vinod