linux-kernel - Re: Would an "information module" be useful?

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: <523F5361.8040906@web.de>
Date:	Sun, 22 Sep 2013 22:30:25 +0200
From:	Markus Elfring <Markus.Elfring@....de>
To:	linux-kernel@...r.kernel.org
Subject: Re: Would an "information module" be useful?

> You can do all parsing in user space too.

Is it questionable when a custom prefix of a boot command-line parameter can not
be mapped to a kernel module?

> But I'm sure it will not get merged.

Thanks for your feedback.

> All you need is a dummy module with a few module_param()s.

My ideas went in such a direction.

> drivers/misc/ is a nice place do dump such things. :-)

Is an information sink module (with corresponding data type checks) still an
"ordinary" driver?

Regards,
Markus

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/