linux-kernel - Re: How to pass software configuration to driver built as module in boot up phase

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: <2023103137-dowry-passover-c285@gregkh>
Date:   Tue, 31 Oct 2023 11:44:18 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Tingwei Zhang <quic_tingweiz@...cinc.com>
Cc:     Masami Hiramatsu <mhiramat@...nel.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        linux-kernel@...r.kernel.org, Trilok Soni <quic_tsoni@...cinc.com>,
        Jinlong Mao <quic_jinlmao@...cinc.com>
Subject: Re: How to pass software configuration to driver built as module in
 boot up phase

On Tue, Oct 31, 2023 at 06:01:44PM +0800, Tingwei Zhang wrote:
> > Why do you need this before init?  Specific reasons please.
> > 
> There are some case that some driver broke Kernel in development phase and
> those bad driver could cause device crash in very early boot up phase.

Then work on that in the development phase of your system, don't make it
a requirement for us for this.

thanks,

greg k-h