linux-kernel - Re: [PATCH] x86: introduce /dev/mem restrictions with a config option

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]

Message-ID: <47A24615.4060603@zytor.com>
Date:	Thu, 31 Jan 2008 14:05:09 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	Arjan van de Ven <arjan@...radead.org>,
	Jan Engelhardt <jengelh@...putergmbh.de>,
	linux-kernel@...r.kernel.org, davej@...hat.com, mingo@...e.hu,
	tglx@...x.de
Subject: Re: [PATCH] x86: introduce /dev/mem restrictions with a config option

Jesse Barnes wrote:
>>> This is more for compatibility with legacy X
>> Legacy X, and non-BAR X memory (originally ISA, of course; now
>> probably more often "stolen system memory").
> 
> For legacy memory, we actually have /sys/bus/pci/<busno>/legacy_mem 
> (though ia64 may be the only supported platform).  It's actually 
> required on some arches due to the way this space is allocated across 
> the system.

Well, it's certainly not under /sys/bus/pci on x86 systems...

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