| 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: <c384c5ea0808210731k17ccc836u60c4803c3abfea31@mail.gmail.com> Date: Thu, 21 Aug 2008 16:31:44 +0200 From: "Leon Woestenberg" <leon.woestenberg@...il.com> To: "Jared Hulbert" <jaredeh@...il.com> Cc: Linux-kernel@...r.kernel.org, linux-embedded@...r.kernel.org, linux-mtd <linux-mtd@...ts.infradead.org>, "Jörn Engel" <joern@...fs.org>, tim.bird@...sony.com, cotte@...ibm.com, nickpiggin@...oo.com.au Subject: Re: [PATCH 00/10] AXFS: Advanced XIP filesystem Hello Jared, On Thu, Aug 21, 2008 at 4:19 PM, Jared Hulbert <jaredeh@...il.com> wrote: >> FWIW, I'm not sure it's a good idea to name this new filesystem AXFS. >> People are almost certainly going to confuse it with XFS despite > People that care about their filesystem choice know their choices. People that don't care, well they don't care. Maybe AXIPFS would be the close alternative. One question on the use-case profiling and subsequent image rebuild: What if the use-case did not cover all cases of XIP use? If a compressed page is attempted to be executed, will the filesystem fall back to decompression to RAM and execution from RAM, or will this result in a faulty system? The design choices look real good. Congrats on the achievement. Regards, -- Leon -- 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