linux-kernel - 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-next>] [day] [month] [year] [list]

Date:   Mon, 30 Oct 2023 19:21:48 +0800
From:   Tingwei Zhang <quic_tingweiz@...cinc.com>
To:     Masami Hiramatsu <mhiramat@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>
CC:     <linux-kernel@...r.kernel.org>,
        Trilok Soni <quic_tsoni@...cinc.com>,
        Jinlong Mao <quic_jinlmao@...cinc.com>
Subject: How to pass software configuration to driver built as module in boot
 up phase

Hi Masami, Greg and Rafael,

I have one driver that needs a bunch to software configuration like 1000 
settings. These settings can be different according to the use case.

They are required in boot up phase so we can't reply on user space to 
make the configuration.

Boot config is not preferred since we'd like to build that driver as 
dynamic load Kernel module.

Could you let me know if there's any mechanism in Kernel to do that?

-- 
Thanks,
Tingwei