Bug 292011 – sys-fs/squashfs-tools-4.0: unsquashfs error "failed to read fragment table"

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Nicolas Dufresne 2009-11-05 19:22:41 UTC]

unsquashfs often fails with error "failed to read fragment table". This error is due to missing return value to a non-void return statement in read_fragment_table_4(). I have a patch for this, along with a division by zero fix when 0 element is being "unsquashed".

Reproducible: Always

Steps to Reproduce:
1. Get a squashfs image version 4
2. Try to unsquash it

Actual Results:  
FATAL ERROR aborting: failed to read fragment table

Expected Results:  
Successful unsquash

[Comment 1 Nicolas Dufresne 2009-11-05 19:23:33 UTC]

Created attachment 209361 [details, diff]
Fix missing return value to non-void return statement

This change is already in upstream CVS

[Comment 2 Nicolas Dufresne 2009-11-05 19:24:35 UTC]

Created attachment 209362 [details, diff]
Fix division by zero in status bar when no file has to be extracted

This patch is from upstream CVS.

[Comment 3 Nicolas Dufresne 2009-11-05 19:27:27 UTC]

Created attachment 209364 [details]
Updated ebuild that includes the previous patches

This ebuild was tested out of my overlay using a x86_64 machine and works as expected.

[Comment 4 SpanKY 2009-12-07 23:23:18 UTC]

while i see the first change in the upstream cvs, i dont see the second.  could you post info on that ?

[Comment 5 Nicolas Dufresne 2009-12-08 02:14:13 UTC]

Sorry, went too fast, patch is from Matthew Creech, found on Nabble:

http://old.nabble.com/-PATCH--squashfs:-Handle-progress-bar-when-max-%3D%3D-0-td22901074.html

Sadly its not upstream yet, but it can be reproduced if you extract something like / folder from a squash image.

[Comment 6 SpanKY 2010-09-20 02:03:40 UTC]

should be added in 4.0-r1 now; thanks