| 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
| ||
|
Message-ID: <20070502143839.GA31961@atjola.homenet> Date: Wed, 2 May 2007 16:38:39 +0200 From: Björn Steinbrink <B.Steinbrink@....de> To: Hugh Dickins <hugh@...itas.com> Cc: Phillip Susi <psusi@....rr.com>, Linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: Execute in place On 2007.05.02 15:04:44 +0100, Hugh Dickins wrote: > On Tue, 1 May 2007, Phillip Susi wrote: > > I seem to remember seeing some patches go by at some point that > > allowed one of the rom type embeded system filesystems to directly > > execute binaries out of the original rom memory rather than copying > > them to ram first, then executing from there. I was wondering if > > rootfs or tmpfs support such execute in place today, or if binaries > > executed from there have their code segments duplicated in ram? > > Only ext2 supports it today: see Documentation/filesystems/xip.txt As I understand it, xip avoids the page cache copy. But tmpfs already lives in the page cache (or swap), so avoiding that "copy" is impossible. But I always expected tmpfs to implicitly due its own kind of xip, i.e. that it doesn't have to store its stuff in the page cache twice. Are you saying that this isn't true? According to Documentation/filesystems/xip.txt the ramdisk driver does something similar, pushing the data into the page cache and discarding the original data. thanks, Björn - 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/
Powered by blists - more mailing lists