linux-kernel - Re: [PATCH 06/14] pci: reject mmio range start from 0 on pci

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:	Fri, 15 Jan 2010 13:15:45 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ivan Kokshaysky <ink@...assic.park.msu.ru>,
	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
	Alex Chiang <achiang@...com>,
	Bjorn Helgaas <bjorn.helgaas@...com>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH 06/14] pci: reject mmio range start from 0 on pci_bridge
 read

On 01/15/2010 11:19 AM, Jesse Barnes wrote:
> On Tue, 22 Dec 2009 15:02:26 -0800
> Yinghai Lu <yinghai@...nel.org> wrote:
> 
>> that is wrong.
>>
>> exposed by that patch that doesn's shrink pci bridge res.
>>
>> -v2: change to "bar reading" to "reg reading"
>>
>> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
>> ---
> 
> Is this really necessary?  Won't we conflict with the reserved zero
> page anyway?
> 

just try to print out the work for pci bridge BAR by BIOS, and just like we did for pci device BAR

before we touch it.

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