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: <6934efce0706140953x2167944fr54eca6376e1f8d63@mail.gmail.com>
Date:	Thu, 14 Jun 2007 09:53:33 -0700
From:	"Jared Hulbert" <jaredeh@...il.com>
To:	carsteno@...ibm.com
Cc:	"Nick Piggin" <nickpiggin@...oo.com.au>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	richard.griffiths@...driver.com,
	"Richard Griffiths" <res07ml0@...izon.net>,
	linux-kernel@...r.kernel.org,
	"Jörn Engel" <joern@...ybastard.org>
Subject: Re: [PATCH 2.6.21] cramfs: add cramfs Linear XIP

> An alternative approach, which does not need to have struct page at
> hand, would be to use the nopfn vm operations struct. That one would
> have to rely on get_xip_pfn.

Of course!  Okay now I'm begining to understand.

> The current path would then be deprecated.

Why?  Wouldn't both paths be valid options?

> If you're interrested in using the later for xip without
> struct page, I would volounteer to go ahead and implement this?

I'm very interested in this.

 I'm not opposed to using struct page, but I'm confused as to how to
start that.  As I understand it, which is not well, defined a
CONFIG_DISCONTIGMEM region to cover the Flash memory would add that to
my pool of RAM.  That would be 'bad', right?  I don't see how to
create the page structs and set this memory aside as different.
-
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/