From: Phillip Lougher <phil.lougher@gmail.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Phillip Lougher <phillip@lougher.demon.co.uk>,
Stefan Lippers-Hollmann <s.L-H@gmx.de>,
Linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] Squashfs fixes for 2.6.29?
Date: Tue, 10 Mar 2009 21:33:06 +0000 [thread overview]
Message-ID: <cce9e37e0903101433r68f6140and965959f9063e798@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.00.0903101149500.25436@vixen.sonytel.be>
Geert Uytterhoeven wrote:
> On Tue, 10 Mar 2009, Phillip Lougher wrote:
>> Stefan Lippers-Hollmann wrote:
>>> This patch seems to break squashfs for me on i386 and amd64.
>>> Test environment is a squashed filesystem image (live CD image, but also
>>> tested manually with a loop mounted iso9660 and loop mounted squashfs;
>>> kernel 2.6.29-rc7-git2). The squashfs image has been created with
>>> squashfs-tools CVS[1] as of today (latest commit 2009-03-03).
>>>
>> Can you send me a filesystem (or link to one) which exhibits this? Zlib is
>> obviously showing unexpected behaviour...
>
> I see the same thing here. I'll send you a test file system by private email.
>
OK thanks, I've received it, and reproduced the problem :-)
> The patch below fixes it. It seems zlib sometimes does need an additional
> loop ;-)
>
Yes thanks.
> Note that I expect it may now loop forever in case of file system corruption.
This is the next thing, to redo the file system corruption patch.
Thanks
Phillip
next prev parent reply other threads:[~2009-03-10 21:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 1:54 Phillip Lougher
2009-03-09 21:39 ` Stefan Lippers-Hollmann
2009-03-10 2:13 ` Phillip Lougher
2009-03-10 11:02 ` Geert Uytterhoeven
2009-03-10 13:19 ` Woody Suwalski
2009-03-10 21:24 ` Stefan Lippers-Hollmann
2009-03-10 21:33 ` Phillip Lougher [this message]
2009-03-11 6:12 ` Phillip Lougher
2009-03-11 14:18 ` Geert Uytterhoeven
2009-03-11 20:46 ` Stefan Lippers-Hollmann
2009-03-10 20:02 ` Stefan Lippers-Hollmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cce9e37e0903101433r68f6140and965959f9063e798@mail.gmail.com \
--to=phil.lougher@gmail.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=akpm@linux-foundation.org \
--cc=phillip@lougher.demon.co.uk \
--cc=s.L-H@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®