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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YDYHhYRDBDKGSZ1r@kroah.com>
Date:   Wed, 24 Feb 2021 09:00:05 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     "Enrico Weigelt, metux IT consult" <info@...ux.net>
Cc:     linux-kernel@...r.kernel.org, rafael@...nel.org,
        linus.walleij@...aro.org, bgolaszewski@...libre.com,
        robh+dt@...nel.org, frowand.list@...il.com,
        pantelis.antoniou@...sulko.com, linux-gpio@...r.kernel.org,
        devicetree@...r.kernel.org
Subject: Re: [RFC PATCH 09/12] drivers: base: reintroduce find_bus()

On Tue, Feb 23, 2021 at 09:13:26PM +0100, Enrico Weigelt, metux IT consult wrote:
> On 13.02.21 11:20, Greg KH wrote:
> > On Mon, Feb 08, 2021 at 11:22:00PM +0100, Enrico Weigelt, metux IT consult wrote:
> > > ---
> > >   drivers/base/bus.c         | 14 ++++++++++----
> > >   include/linux/device/bus.h |  2 ++
> > >   2 files changed, 12 insertions(+), 4 deletions(-)
> > 
> > Um, no.
> 
> Why not ? Do you have a better idea ?
> 
> What I actually need is a way to unbdind a specific device, identified
> by bus name and device name. The problem to be solved here is dropping
> devices that have been enumerated in a bad way by firmware (ACPI in this
> case), and then recreating it in a clean, consistent way.

Have the firmware code do it itself, do nto try to "reach across" like
this.

And what problem are you really trying to solve here by doing this?

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ