linux-kernel - Re: 2.6.18-rc5-mm1: strange /proc/interrupts contents on HPC nx6325

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]

Message-Id: <20060906201953.d96ee183.akpm@osdl.org>
Date:	Wed, 6 Sep 2006 20:19:53 -0700
From:	Andrew Morton <akpm@...l.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: 2.6.18-rc5-mm1: strange /proc/interrupts contents on HPC nx6325

On Wed, 6 Sep 2006 21:17:30 +0200
"Rafael J. Wysocki" <rjw@...k.pl> wrote:

> Hi,
> 
> [I'm not quite sure who should be on the Cc list.]

I know ;)

> The contents of /proc/interrupts look strange on the HPC nx6325 I'm currently using
> (2.6.18-rc5-mm1, 64-bit kernel):
> 
>            CPU0       CPU1       
>   0:      18073          0    <NULL>-edge     timer
>   1:        163          0   IO-APIC-edge     i8042
>   8:          0          0   IO-APIC-edge     rtc
>   9:        120          0   IO-APIC-fasteoi  acpi
>  12:        149          0   IO-APIC-edge     i8042
>  14:         24          0   IO-APIC-edge     ide0
>  16:       4796          0   IO-APIC-fasteoi  libata
>  19:         75          0   IO-APIC-fasteoi  ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
>  20:          7          0   IO-APIC-fasteoi  yenta, ohci1394, sdhci:slot0
>  23:        672          0   IO-APIC-fasteoi  eth0
> 4348:        188          0   PCI-MSI-<NULL>  HDA Intel
> NMI:         89         59 
> LOC:      18036      18171 
> ERR:          0

This is due to a gruesome hack (IMO) in the genirq code (handle_irq_name())
which magically "knows" about the various types of IRQ handler, but doesn't
know about the MSI ones.  It should be converted to a field in irq_desc, or
a callback or something.  

I already had a whine about this then forgot about it, but it seems that
code can't be changed by whining at it ;)

-
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/