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: <20666f18-7762-7e26-64e0-5cb7adc46548@intel.com>
Date: Fri, 5 Apr 2024 13:05:29 -0700
From: Fenghua Yu <fenghua.yu@...el.com>
To: Jerry Snitselaar <jsnitsel@...hat.com>, Dave Jiang <dave.jiang@...el.com>
CC: Vinod Koul <vkoul@...nel.org>, <dmaengine@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dmaengine: idxd: Check for driver name match before sva
 user feature

On 4/2/24 10:07 PM, Jerry Snitselaar wrote:
> Currenty if the user driver is probed on a workqueue configured for

s/Currenty/Currently/

> 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.
>
> Move the SVA feature check to be after the driver name match
> check.
>
> Cc: Vinod Koul <vkoul@...nel.org>
> Cc: dmaengine@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org
> Signed-off-by: Jerry Snitselaar <jsnitsel@...hat.com>

Other than the typo,

Reviewed-by: Fenghua Yu <fenghua.yu@...el.com>

Thanks.

-Fenghua

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ