linux-kernel - Re: [PATCH v2] uio: ensure class is registered before 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180816083438.GE21707@piout.net>
Date:   Thu, 16 Aug 2018 10:34:38 +0200
From:   Alexandre Belloni <alexandre.belloni@...tlin.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] uio: ensure class is registered before devices

On 16/08/2018 10:01:12+0200, Greg Kroah-Hartman wrote:
> On Thu, Aug 16, 2018 at 09:39:41AM +0200, Alexandre Belloni wrote:
> > When both uio and the uio drivers are built in the kernel, it is possible
> > for a driver to register devices before the uio class is registered.
> 
> How does this happen?  The link order should solve this issue, right?
> 

Sure, if we can ensure uio_init() is called before any driver calls
uio_register_device() then this would not happen. However, I'm not sure
how you would want to achieve that.

-- 
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com