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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Sat, 25 Nov 2017 12:03:12 +1100 (AEDT)
From:   Finn Thain <>
To:     Greg Kroah-Hartman <>
cc:     Geert Uytterhoeven <>,,
Subject: Re: [PATCH v2 13/13] nubus: Add support for the driver model

On Fri, 24 Nov 2017, Greg Kroah-Hartman wrote:

> > > 
> > > But what happens when the bus code is unloaded if it is built as a 
> > > module?  The devices will be removed then.  Or they should be.
> > > 
> > 
> > This bus driver is not a module.
> It can not be built as a module ever?

That's right:

$ cat arch/m68k/Kconfig.bus
config NUBUS
        depends on MAC
        default y

I don't plan to convert this bus driver to a module, but this patch series 
would make that conversion more difficult, should it happen in future.

Therefore I plan to revise this submission to avoid or remove the existing 
global nubus_boards list, because the use of this list means that a 
hypothetical device_put() call is not allowable.

You may wish to disregard this submission.



Powered by blists - more mailing lists