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: <465BB5BA.3050900@yahoo.com.au>
Date:	Tue, 29 May 2007 15:10:18 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	carsteno@...ibm.com
CC:	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

Carsten Otte wrote:

> The current xip stack relies on having struct page behind the memory 
> segment. This causes few impact on memory management, but occupies some 
> more memory. The cramfs patch chose to modify copy on write in order to 
> deal with vmas that don't have struct page behind.
> So far, Hugh and Linus have shown strong opposition against copy on 
> write with no struct page behind. If this implementation is acceptable 
> to the them, it seems preferable to me over wasting memory. The xip 
> stack should be modified to use this vma flag in that case.

I would rather not :P

We can copy on write without a struct page behind the source today, no?
What is insufficient for the XIP code with the current COW?

-- 
SUSE Labs, Novell Inc.
-
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/