| 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
| ||
|
Date: Tue, 2 Sep 2008 10:47:45 -0700 From: "Jared Hulbert" <jaredeh@...il.com> To: "Jörn Engel" <joern@...fs.org> Cc: "Geert Uytterhoeven" <Geert.Uytterhoeven@...ycom.com>, Linux-kernel@...r.kernel.org, linux-embedded@...r.kernel.org, linux-mtd <linux-mtd@...ts.infradead.org>, tim.bird@...sony.com, cotte@...ibm.com, nickpiggin@...oo.com.au Subject: Re: [PATCH 00/10] AXFS: Advanced XIP filesystem >> How is one expected to read those last 4 bytes of a loopbacked file? >> Are they unreadable? We can add the padding. I am just wondering if >> this is a bug or a known limitation in the loopback handling or if >> there is a different safer way of reading block devs with truncated >> last blocks. > > Can't you just include the final magic into the last block, thereby > making the size a clean multiple of 4k? It looks as if you have some > padding before the magic anyway. So you just have to make sure the > padding is at least 4 bytes and write the magic to the end of it. Apart > from solving this bug, it should also save you some space. ;) I'm going to have to look into this n*4K thing. The image doesn't need to be aligned. There shouldn't be any last block to put the magic in. But I haven't messed with the mkfs.axfs code for a while. -- 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