linux-kernel - Re: [PATCH 2.6.27-rc4] irq: irq and pci_ids patch for Intel Ibex Peak DeviceIDs

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:	Thu, 28 Aug 2008 07:12:47 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	Seth Heasley <seth.heasley@...el.com>, i2c@...sensors.org,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH 2.6.27-rc4] irq: irq and pci_ids patch for Intel Ibex  Peak DeviceIDs

On Thursday, August 28, 2008 12:49 am Jean Delvare wrote:
> Hi Seth,
>
> On Wed, 27 Aug 2008 16:58:26 -0700, Seth Heasley wrote:
> > This patch updates the Intel Ibex Peak (PCH) LPC and SMBus Controller
> > DeviceIDs.
> >
> > Signed-off-by: Seth Heasley <seth.heasley@...el.com>
> >
> > --- linux-2.6/include/linux/pci_ids.h.orig	2008-08-27 11:54:07.000000000
> > -0700 +++ linux-2.6/include/linux/pci_ids.h	2008-08-27 12:01:53.000000000
> > -0700 @@ -2428,9 +2428,39 @@
> >  #define PCI_DEVICE_ID_INTEL_ICH10_3	0x3a1a
> >  #define PCI_DEVICE_ID_INTEL_ICH10_4	0x3a30
> >  #define PCI_DEVICE_ID_INTEL_ICH10_5	0x3a60
> > -#define PCI_DEVICE_ID_INTEL_PCH_0	0x3b10
> > -#define PCI_DEVICE_ID_INTEL_PCH_1	0x3b11
> > -#define PCI_DEVICE_ID_INTEL_PCH_2	0x3b30
> > +#define PCI_DEVICE_ID_INTEL_PCH_0	0x3b00
> > +#define PCI_DEVICE_ID_INTEL_PCH_1	0x3b01
> > +#define PCI_DEVICE_ID_INTEL_PCH_2	0x3b02
>
> Changing device ID definitions that way is really bad practice. It
> needs to be synchronized between all involved subsystems.
>
> > --- linux-2.6/arch/x86/pci/irq.c.orig	2008-08-27 11:53:13.000000000 -0700
> > +++ linux-2.6/arch/x86/pci/irq.c	2008-08-27 12:07:21.000000000 -0700
> > @@ -592,6 +592,36 @@
> >  	case PCI_DEVICE_ID_INTEL_ICH10_3:
> >  	case PCI_DEVICE_ID_INTEL_PCH_0:
> >  	case PCI_DEVICE_ID_INTEL_PCH_1:
> > +	case PCI_DEVICE_ID_INTEL_PCH_2:
> > +	case PCI_DEVICE_ID_INTEL_PCH_3:
> > +	case PCI_DEVICE_ID_INTEL_PCH_4:
> > +	case PCI_DEVICE_ID_INTEL_PCH_5:
> > +	case PCI_DEVICE_ID_INTEL_PCH_6:
> > +	case PCI_DEVICE_ID_INTEL_PCH_7:
> > +	case PCI_DEVICE_ID_INTEL_PCH_8:
> > +	case PCI_DEVICE_ID_INTEL_PCH_9:
> > +	case PCI_DEVICE_ID_INTEL_PCH_10:
> > +	case PCI_DEVICE_ID_INTEL_PCH_11:
> > +	case PCI_DEVICE_ID_INTEL_PCH_12:
> > +	case PCI_DEVICE_ID_INTEL_PCH_13:
> > +	case PCI_DEVICE_ID_INTEL_PCH_14:
> > +	case PCI_DEVICE_ID_INTEL_PCH_15:
> > +	case PCI_DEVICE_ID_INTEL_PCH_16:
> > +	case PCI_DEVICE_ID_INTEL_PCH_17:
> > +	case PCI_DEVICE_ID_INTEL_PCH_18:
> > +	case PCI_DEVICE_ID_INTEL_PCH_19:
> > +	case PCI_DEVICE_ID_INTEL_PCH_20:
> > +	case PCI_DEVICE_ID_INTEL_PCH_21:
> > +	case PCI_DEVICE_ID_INTEL_PCH_22:
> > +	case PCI_DEVICE_ID_INTEL_PCH_23:
> > +	case PCI_DEVICE_ID_INTEL_PCH_24:
> > +	case PCI_DEVICE_ID_INTEL_PCH_25:
> > +	case PCI_DEVICE_ID_INTEL_PCH_26:
> > +	case PCI_DEVICE_ID_INTEL_PCH_27:
> > +	case PCI_DEVICE_ID_INTEL_PCH_28:
> > +	case PCI_DEVICE_ID_INTEL_PCH_29:
> > +	case PCI_DEVICE_ID_INTEL_PCH_30:
> > +	case PCI_DEVICE_ID_INTEL_PCH_31:
>
> I am no PCI IRQ routing expert, but I have to admit that I a bit
> skeptical that all the PCH functions are IRQ routers. You're adding as
> many entries here for the PCH than there have been for all Intel chips
> in the past 10 years or so...
>
> >  		r->name = "PIIX/ICH";
> >  		r->get = pirq_piix_get;
> >  		r->set = pirq_piix_set;

Yeah, this has me confused now too.  I remember specifically asking if the 
other PCHs needed to be added to this list when the last patch was applied.  
What happened?  Can you give us some more background here, Seth?  The 
changelog should definitely include an explanation of why the IDs need to be 
changed (i.e. why the old commit was wrong).

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/