linux-kernel - Re: [PATCH v2] parport: register driver later

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]

Date:	Tue, 5 Apr 2016 07:07:45 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Sudip Mukherjee <sudipm.mukherjee@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	stable <stable@...r.kernel.org>,
	Ross Zwisler <ross.zwisler@...ux.intel.com>
Subject: Re: [PATCH v2] parport: register driver later

On Tue, Apr 5, 2016 at 6:47 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
>>
>> I was hoping that would be it. Have there been reports since that I
>> haven't seen?
>
> Not that I have seen.

Ok. So as far as I can see we can ignore this for now (at at least be
no worse off than we used to be).

I didn't check *why* ppdev_init happens before the parport driver has
been initialized,

I get the feeling that the trivial fix would be to just make a new
"parport_init/exit()" pair that just does the parport_bus_init(). And
mark that as "subsys_initcall()" so that it gets done before the
individual drivers. No need to even be fancy about deferred probing
etc, just a simple "ppdev depends on parport" chain.

But I didn't look into the actual sequence of events, so it's entirely
possible I'm missing something.

                 Linus