linux-kernel - Re: [discuss] Re: Please pull x86-64 bug fixes

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: <200610060052.46538.ak@suse.de>
Date:	Fri, 6 Oct 2006 00:52:46 +0200
From:	Andi Kleen <ak@...e.de>
To:	Linus Torvalds <torvalds@...l.org>
Cc:	Jeff Garzik <jeff@...zik.org>, discuss@...-64.org,
	linux-kernel@...r.kernel.org
Subject: Re: [discuss] Re: Please pull x86-64 bug fixes


> In other words, right now we have
> 
> 	int pci_read_config_byte(struct pci_dev *dev, int where, u8 *val)
> 
> and maybe we will simply have to add a totally new function like
> 
> 	int pci_read_mmio_config_byte(struct pci_dev *dev, int where, u8 *val)
> 
> for drivers that literally _require_ the mmio accesses for one reason or 
> another.

That's easy to decide: if (where >= 256) mmconfig is required. 

I'm just afraid it probably won't help if the MCFG is totally broken and
points to some other devices (like on the Intel boards). Then these drivers will 
just hang and all of Alan's warning  messages won't help with that.

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