linux-kernel - Re: [PATCH] RFC: platform driver registering via initcall tables

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]

Message-ID: <20191217145003.GB3639802@kroah.com>
Date:   Tue, 17 Dec 2019 15:50:03 +0100
From:   Greg KH <greg@...ah.com>
To:     "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
Cc:     "Enrico Weigelt, metux IT consult" <info@...ux.net>,
        linux-kernel@...r.kernel.org, linus.walleij@...aro.org,
        bgolaszewski@...libre.com, dmitry.torokhov@...il.com,
        jacek.anaszewski@...il.com, pavel@....cz, dmurphy@...com,
        arnd@...db.de, masahiroy@...nel.org, michal.lkml@...kovi.net,
        kafai@...com, songliubraving@...com, yhs@...com, andriin@...com,
        linux-gpio@...r.kernel.org, linux-input@...r.kernel.org,
        linux-leds@...r.kernel.org, linux-arch@...r.kernel.org,
        linux-kbuild@...r.kernel.org, netdev@...r.kernel.org,
        bpf@...r.kernel.org
Subject: Re: [PATCH] RFC: platform driver registering via initcall tables

On Tue, Dec 17, 2019 at 03:43:56PM +0100, Enrico Weigelt, metux IT consult wrote:
> On 17.12.19 15:06, Greg KH wrote:
> 
> > That's not needed, and you are going to break the implicit ordering we
> > already have with link order.  
> 
> Ups, 10 points for you - I didn't consider that.
> 
> > You are going to have to figure out what
> > bus type the driver is, to determine what segment it was in, to figure
> > out what was loaded before what.
> 
> hmm, if it's just the ordering by bus type (but not within one bus
> type), then it shouldn't be the big deal to fix, as I'll need one table
> and register-loop per bus-type anyways.
> 
> By the way: how is there init order ensured with dynamically loaded
> modules ? (for cases where there aren't explicit symbol dependencies)

See the recent work in the driver core for DT fixes for that very issue.

greg k-h