linux-kernel - Re: remap_pfn_range() not suitable for physical RAM?

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: <200903100904.22753.frank.mehnert@sun.com>
Date:	Tue, 10 Mar 2009 09:04:19 +0100
From:	Frank Mehnert <Frank.Mehnert@....COM>
To:	linux-kernel@...r.kernel.org
Cc:	peterz@...radead.org, suresh.b.siddha@...el.com
Subject: Re: remap_pfn_range() not suitable for physical RAM?

Hi,

sorry for re-posting this message and sorry for addressing you directly.
Perhaps you can help me again or can you give me a pointer for a proper
documentation of the various *remap* and *vm_insert* functions:

On Wednesday 04 March 2009, Frank Mehnert wrote:
> since 2.6.29-rcX it seems to be not allowed anymore to use
> remap_pfn_range() to remap physical RAM to userland. This restriction
> applies only if CONFIG_X86_PAT is enabled. It seems that vm_insert_page()
> does not have this restriction. Am I correct? And what is the reason
> for this restriction?

Kind regards,

Frank
-- 
Dr.-Ing. Frank Mehnert    Sun Microsystems    http://www.sun.com/

Download attachment "signature.asc " of type "application/pgp-signature" (198 bytes)