[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <D1H452IHSLRC.1WZSPJQLCD5RD@kernel.org>
Date: Thu, 23 May 2024 18:01:49 +0300
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: <linux-modules@...r.kernel.org>
Cc: "Luis Chamberlain" <mcgrof@...nel.org>, "Linus Torvalds"
<torvalds@...ux-foundation.org>, <linux-kernel@...r.kernel.org>, "Herbert
Xu" <herbert@...dor.apana.org.au>, <linux-crypto@...r.kernel.org>
Subject: is_module()
Hi,
I just put this here while I still have it on my mind. Possibly I'm
ignoring something that already enables this but at least I learn
something by doing this then.
This came up in a recent discussion albeit for this crypto bug it
did not make waves because the bug fix did not require it:
https://lore.kernel.org/linux-integrity/D1GXKODMD4S8.1J12D4GOEQWPL@kernel.org/
So the gist of is_module() would be that it would have different
semantics than IS_MODULE(): it could be used to e.g. check modules in a
loop.
Compilation would generate a new ELF section with following entries:
<ASCIIZ string><0 or 1>
The string would contain module name, and 1 could be marking for
being a module, and 0 for being builtin.
Also, it would enabled to add lsmod -b to enumerate built-in modules,
which would give nice way to carve up more information about a running
test kernel. This would obviously need perhaps a new file to procfs for
built-in modules (for regular there is /proc/modules).
Not fighting for having this, just makig it visible.
BR, Jarkko
Powered by blists - more mailing lists