From: Stefan Lippers-Hollmann <s.L-H@gmx.de>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Phillip Lougher <phillip@lougher.demon.co.uk>,
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 22:24:21 +0100 [thread overview]
Message-ID: <200903102224.22994.s.L-H@gmx.de> (raw)
In-Reply-To: <alpine.LRH.2.00.0903101149500.25436@vixen.sonytel.be>
Hi
On Dienstag, 10. März 2009, 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.
>
> The patch below fixes it. It seems zlib sometimes does need an additional
> loop ;-)
>
> Note that I expect it may now loop forever in case of file system corruption.
This patch seems to work for me, no further errors while copying files and
no syslog messages.
Regards
Stefan Lippers-Hollmann
--
> Signed-off-by: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
>
> diff --git a/fs/squashfs/block.c b/fs/squashfs/block.c
> index 321728f..46358dd 100644
> --- a/fs/squashfs/block.c
> +++ b/fs/squashfs/block.c
> @@ -184,15 +184,7 @@ int squashfs_read_data(struct super_block *sb, void **buffer, u64 index,
> offset = 0;
> }
>
> - if (msblk->stream.avail_out == 0) {
> - if (page == pages) {
> - ERROR("zlib_inflate tried to "
> - "decompress too much data, "
> - "expected %d bytes. Zlib "
> - "data probably corrupt\n",
> - srclength);
> - goto release_mutex;
> - }
> + if (msblk->stream.avail_out == 0 && page < pages) {
> msblk->stream.next_out = buffer[page++];
> msblk->stream.avail_out = PAGE_CACHE_SIZE;
> }
>
> With kind regards,
>
> Geert Uytterhoeven
> Software Architect
>
> Sony Techsoft Centre Europe
> The Corporate Village · Da Vincilaan 7-D1 · B-1935 Zaventem · Belgium
>
> Phone: +32 (0)2 700 8453
> Fax: +32 (0)2 700 8622
> E-mail: Geert.Uytterhoeven@sonycom.com
> Internet: http://www.sony-europe.com/
>
> A division of Sony Europe (Belgium) N.V.
> VAT BE 0413.825.160 · RPR Brussels
> Fortis · BIC GEBABEBB · IBAN BE41293037680010
next prev parent reply other threads:[~2009-03-10 21:25 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 [this message]
2009-03-10 21:33 ` Phillip Lougher
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=200903102224.22994.s.L-H@gmx.de \
--to=s.l-h@gmx.de \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=akpm@linux-foundation.org \
--cc=phillip@lougher.demon.co.uk \
/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
Powered by JetHome