From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: [PATCH 00/10] AXFS: Advanced XIP filesystem Date: Tue, 2 Sep 2008 19:15:01 +0200 Message-ID: <20080902171500.GC19618@logfs.org> References: <48AD00C4.6060302@gmail.com> <6934efce0808220951i5a2cd6f9t70f9c522eae6f1d6@mail.gmail.com> <6934efce0809020944s36dd7f82wec77c4189ef1b114@mail.gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <6934efce0809020944s36dd7f82wec77c4189ef1b114@mail.gmail.com> Sender: linux-embedded-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1" To: Jared Hulbert Cc: Geert Uytterhoeven , Linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org, linux-mtd , tim.bird@am.sony.com, cotte@de.ibm.com, nickpiggin@yahoo.com.au On Tue, 2 September 2008 09:44:19 -0700, Jared Hulbert wrote: >=20 > 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 i= f > 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. Apar= t from solving this bug, it should also save you some space. ;) J=C3=B6rn --=20 Invincibility is in oneself, vulnerability is in the opponent. -- Sun Tzu