linux-kernel - Re: [PATCH 2.6.21] cramfs: add cramfs Linear 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]

Message-ID: <46553744.4000403@de.ibm.com>
Date:	Thu, 24 May 2007 08:57:08 +0200
From:	Carsten Otte <cotte@...ibm.com>
To:	Jared Hulbert <jaredeh@...il.com>
CC:	carsteno@...ibm.com, Andrew Morton <akpm@...ux-foundation.org>,
	richard.griffiths@...driver.com,
	Richard Griffiths <res07ml0@...izon.net>,
	Linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.21] cramfs: add cramfs Linear XIP

Jared Hulbert wrote:
>> To me, it looks like this
>> work can be modified to use filemap_xip.
> 
> How?
First, get a struct page behind the subject file system image. A good 
idea to get there is to use vmem_map, which allows have a 
discontiguous mem_map array in virtual storage. Then add the memory 
segment's address range to it. Sparsemem also helps, if vmem_map is 
not available.

Second, implement get_xip_page for this file system. This address 
space operation needs to be provided for all files that are supposed 
to be XIP. readpage(s)/writepage(s) should not be provided for these 
files, becuase they rely on using the page cache.

Third, use file operations from mm/filemap_xip.c.

so long,
Carsten
-
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/