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] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024111228-snowcap-counting-b833@gregkh>
Date: Tue, 12 Nov 2024 12:48:11 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Zijun Hu <zijun_hu@...oud.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>, linux-kernel@...r.kernel.org,
	Zijun Hu <quic_zijuhu@...cinc.com>
Subject: Re: [PATCH RESEND v2 0/2] driver core: bus: Fix issues related to
 bus_rescan_devices_helper()

On Tue, Oct 22, 2024 at 07:18:00PM +0800, Zijun Hu wrote:
> This patch series is to fix issues related to bus_rescan_devices_helper().
> 
> The function is improperly used for 2 incompatible scenarios as
> explained below:
> 
> Scenario A: scan drivers for a single device user specify
>  - user may care about precise synchronous scanning result, so the
>    function can not collapse error codes.

I do not understand this, what is wrong that this is fixing?

> Scenario B: scan drivers for all devices of a bus
>  - user may need to scan drivers for a bus's devices as many as
>    possible, so the function needs to ignore inconsequential error
>    codes for a device in order to continue to scan for next device.

How often is that needed?  And why can't that still work with the
existing code?

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ