linux-kernel - [PATCH 0/1] mcb: better use of buses when registering mcb devices

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-next>] [day] [month] [year] [list]

Message-ID: <20231020124324.54692-1-JoseJavier.Rodriguez@duagon.com>
Date:   Fri, 20 Oct 2023 12:44:27 +0000
From:   Rodríguez Barbarin, José Javier 
        <josejavier.rodriguez@...gon.com>
To:     "morbidrsa@...il.com" <morbidrsa@...il.com>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "jth@...nel.org" <jth@...nel.org>,
        Sanjuán García, Jorge 
        <Jorge.SanjuanGarcia@...gon.com>,
        Rodríguez Barbarin, José Javier 
        <josejavier.rodriguez@...gon.com>
Subject: [PATCH 0/1] mcb: better use of buses when registering mcb devices

As Greg suggested in:
https://lore.kernel.org/all/2023100557-mournful-veto-64a2@gregkh/

There was an odd usage of bus_for_each_dev() where the bus used was
being assumed and the input parameter of mcb_bus_add_devices() was
ignored.

Jose Javier Rodriguez Barbarin (1):
  mcb: Use the actual bus passed to init and release functions

 drivers/mcb/mcb-core.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
2.34.1