linux-kernel - Re: System.map

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 14 Oct 2007 20:45:57 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Philip <phibo@...bo.org>
cc:	linux-kernel@...r.kernel.org
Subject: Re: System.map

On Oct 14 2007 19:07, Philip wrote:
>
>I want to write a script, which shows the name of the relevant
>kernel module for each listed pci device shown by 'lspci -m'. It's
>easy to find out the name of the corresponding module, if the driver
>has been compiled as a loadable kernel module: The file
>/lib/modules/$(uname -r)/modules.pcimap lists module names based on
>pci device's vendor -and device id (shown by 'lspci -n'). But how
>can I find out the name of the corresponding kernel module if the
>module has been compiled directly into the kernel ?

Well if it is compiled in, it is not a module, so you cannot find it
the usual way.

>I thought that I
>can find them in the kernel's machting System.map based on vendor
>-and device id as well. But I can't find those id's there. Where do
>I have to look for it ? I want to be informed by my script, if the
>driver (module) for a specific pci device is available as a loadable
>module, in-kernel module or not available at all.

That does not work reliably either. There might be PCI devices
which have the same PID:VID, but need a readb() or so for further
finding out whether the actual piece of hardware has a driver.

And then there is that sort of modules which do not have typical IDs
(i.e. udev cannot/won't autoload them) at all, like pcspkr.ko/psmouse.ko
-
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/