Making life (even) harder for proprietary modules

Posted Aug 3, 2023 22:25 UTC (Thu) by jreiser (subscriber, #11027)
Parent article: Making life (even) harder for proprietary modules

Create a loop-around internal pipe(), run kallsysms and direct the output into the pipe, read the pipe, parse the address and symbol name, call by pointer. Takes around one second or less.

Making life (even) harder for proprietary modules

Posted Aug 3, 2023 23:43 UTC (Thu) by willy (subscriber, #9762) [Link] (2 responses)

What a byzantine approach! Just pass the address of the symbol you need as a module parameter...

Making life (even) harder for proprietary modules

Posted Aug 4, 2023 10:30 UTC (Fri) by dullfire (guest, #111432) [Link]

Sorry Willy, however you are not thinking enough like a "horrible out-of-tree-driver writer" (not to imply ALL out of tree driver writers are horrible, just that the topic is the subset of them that are): you would need to load your symbol(s) by having the module open a file, and then call the read entry points. Then of course you have to parse the file. Because obviously in need to be in a (incorrect use of) XML format.

Making life (even) harder for proprietary modules

Posted Aug 5, 2023 5:18 UTC (Sat) by Cyberax (✭ supporter ✭, #52523) [Link]

Or expose it as a /proc file, to be read by the userspace.