linux-kernel - Re: [PATCH] Always use 64 bit addresses for the firmware memory map

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: <491B8009.803@kernel.org>
Date:	Wed, 12 Nov 2008 17:16:57 -0800
From:	"H. Peter Anvin" <hpa@...nel.org>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Bernhard Walle <bwalle@...e.de>, x86@...nel.org,
	linux-kernel@...r.kernel.org, kexec@...ts.infradead.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Always use 64 bit addresses for the firmware memory map

Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
>> Jeremy Fitzhardinge wrote:
>>  
>>> resource_size_t should always be 64-bit on PAE now.
>>>
>>>     
>>
>> Yes, but this would affect non-PAE kernels too.
>>   
> 
> Yeah, I overlooked the comment about non-PAE.  Should we just make
> resource_size_t 64 bits all the time?  Or ignore inaccessible resources?
> 

Ignore them, presumably (keeping in mind some of them may need to be
truncated.)  We simply don't manage that space.

	-hpa

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