linux-kernel - Re: [patch] rd: support XIP

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:	Tue, 4 Dec 2007 03:26:20 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Nick Piggin <npiggin@...e.de>
Cc:	Christian Borntraeger <borntraeger@...ibm.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>, rob@...dley.net,
	Jens Axboe <axboe@...nel.dk>
Subject: Re: [patch] rd: support XIP

On Tue, 4 Dec 2007 12:21:00 +0100 Nick Piggin <npiggin@...e.de> wrote:

> +	 *
> +	 * Cannot support XIP and highmem, because our ->direct_access
> +	 * routine for XIP must return memory that is always addressable.
> +	 * If XIP was reworked to use pfns and kmap throughout, this
> +	 * restriction might be able to be lifted.
>  	 */
> +	gfp_flags = GFP_NOIO | __GFP_ZERO;
> +#ifndef CONFIG_BLK_DEV_XIP
> +	gfp_flags |= __GFP_HIGHMEM;
> +#endif

A dubious tradeoff?
--
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/