linux-kernel - Re: Why are ipmi modules being loaded?

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]

Date:	Sun, 21 Oct 2007 23:04:02 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: Why are ipmi modules being loaded?

On Sunday 21 October 2007, Dave Jones wrote:
> On Sun, Oct 21, 2007 at 03:34:11PM +0200, Frans Pop wrote:
>  > AFAICT from modules.pcimap, ipmi_si should only be loaded for PCI ID
>  > [103c:121a] (which I don't have), or for devices with class c0700
>  > (which I also don't have).
>
> Hmm, is lspci truncating the class code?
>
>  > 01:00.4 Serial bus controller [0c07]: Intel Corporation 82573E KCS
>  > (Active Management) [8086:108e] (rev 03)

Actually, these three look to be related (see also link below):
01:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet 
Controller (Copper) (rev 03)
01:00.3 Serial controller: Intel Corporation Active Management Technology - 
SOL (rev 03)
01:00.4 Serial bus controller [0c07]: Intel Corporation 82573E KCS (Active 
Management) (rev 03)

I did check the class files in /sys. For these devices those have:
$ cat /sys/bus/pci/devices/0000\:01\:00.0/class
0x020000
$ cat /sys/bus/pci/devices/0000\:01\:00.3/class
0x070002
$ cat /sys/bus/pci/devices/0000\:01\:00.4/class
0x0c0701

The last is close, but still does not match the 0x0c0700 in modules.pcimap. 
Is there some fuzzy matching going on there?

> Because this smells like an IPMI-ish device.

Hmm. Yes, guess it is -ish. It's documented in:
http://download.intel.com/design/motherbd/cz/D1406801US.pdf (section 1.11.4)

Looks like something that is only useful for remote management though and 
not for on-system management.

Anyway, I've blacklisted the modules for now, but still feel that should not 
be necessary and there's an incorrect match happening.

Thanks for the reply Dave.
-
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/