linux-kernel - Re: RFC: x86: cap iomem_resource to addressable physical memory

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] [day] [month] [year] [list]

Date:	Mon, 22 Jun 2009 00:54:14 -0700
From:	"H. Peter Anvin" <hpa@...ux.intel.com>
To:	Pavel Machek <pavel@....cz>
CC:	Yinghai Lu <yhlu.kernel@...il.com>,
	Matthew Wilcox <matthew@....cx>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Martin Mares <mj@....cz>, LKML <linux-kernel@...r.kernel.org>,
	linux-pci@...r.kernel.org,
	the arch/x86 maintainers <x86@...nel.org>,
	David Woodhouse <dwmw2@...radead.org>,
	linux-arch@...r.kernel.org
Subject: Re: RFC: x86: cap iomem_resource to addressable physical memory

Pavel Machek wrote:
> 
> Ok... and is there enough locking in there so that it is actually ok
> to change mask during hotplug? (Is it okay because it is single long
> and all the writers are somehow serialized by hotplug mechanism?)
> 									Pavel

Making it a locked reference probably would be a good idea (although I 
personally think it will never actually matter in practice).  Although 
on 32 bits (PAE) it can be more than one long, it doesn't matter because 
only the upper long can actually be modified.  It does, however, 
complicate the actual code somewhat... I'll look at it tomorrow.

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