Bugger. I just saw this after I sent in my previous message where I
suggested you support the simpler format of:
"kernel: loaded module foo at <hex_address>".
You have a point there: logging the filename of the module would be
quite nice. Unfortunately, while insmod can provide the information,
any logging it generates goes to /var/log/messages, not to
/var/log/kernel. Unless someone knows of a way for a userland process
to send message to the kernel log file (LOG_KERN doesn't seem to
work). The syslog(3) interface doesn't seem to support this.
Still, I don't see much option other than to modify insmod if you
decide you have to have access to filenames: the kernel isn't going to
know.
> And hope that you do not lose any log messages. Either way you still
> have to go to the raw module .o file to get the full symbol map, it is
> the only place that lists static procs.
>
> Using the full /proc/ksyms gave me the extra benefit of checking ksyms
> against the supplied map and modules to ensure they matched. You would
> loose this ability with simple log entries. I think the best option is
> regular and/or exception capture of /proc/ksyms to an external file.
Yes, although I would also like to see a mode where you use and old
logfile and ignore /proc/ksyms entirely, so you can do offline
debugging.
Regards,
Richard....