linux-kernel - Re: [-mm patch] drivers/pci/quirks.c: cleanup

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: <20070110103555.9bc45c6a.khali@linux-fr.org>
Date:	Wed, 10 Jan 2007 10:35:55 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	"Mark M. Hoffman" <mhoffman@...htlink.com>
Cc:	Adrian Bunk <bunk@...sta.de>, greg@...ah.com,
	linux-pci@...ey.karlin.mff.cuni.cz, linux-kernel@...r.kernel.org
Subject: Re: [-mm patch] drivers/pci/quirks.c: cleanup

Hi Mark,

On Tue, 9 Jan 2007 22:58:20 -0500, Mark M. Hoffman wrote:
> * Jean Delvare <khali@...ux-fr.org> [2007-01-09 14:17:21 +0100]:
> > I am worried about the Intel/Asus SMBus quirk then, which affects many
> > more users than the SiS SMBus one, and would suffer from a reordering as
> > well.
> 
> Intel/Asus users on FC[456] would surely have screamed if that was true.  But I
> was curious so I looked deeper.  There is a fundamental difference between the
> Intel SMBus quirks and the SiS SMBus quirk...
> 
> Intel:
> 1) The first quirk keys off the host bridge, setting a flag.  
> 2) The second quirk keys off the LPC, enabling the SMBus if the flag was set.
> 
> SiS:
> 1) The first quirk keys off the *old* LPC ID... this causes the ID to change.[1]
> 2) The second quirk keys off the *new* LPC ID; this one enables the SMBus.
> 
> In the SiS case, both quirks key off the *same* *device*, but with potentially
> different IDs.  The quirk list ordering matters there because the list is
> scanned only once per device.
> 
> For the Intel case, the only ordering that matters is that the host bridge
> device is added [pci_device_add()] before the LPC; AFAICT, that is reliable,
> perhaps even by definition.
> 
> So I don't think you have to worry about the Intel SMBus quirks.

Ah, OK, I think I get it now, thanks for the clarification. I thought
that the quirks were processed in file order for all devices at once,
while I now understand they are processed for each device in turn. In
which case, indeed, as long as the host bridge PCI device is listed
before the ISA bridge PCI device (and as you suggest this appears to be
guaranteed), the Intel SMBus quirk will work fine, regardless of the
linking order.

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