Re: [Squashfs-devel] Handling of hard links in squashfs-3.4

[Phillip L. <ph...@lo...>]

Oliver metz wrote:
> Hi. 
>  
> We are using squashfs to unpack and pack firmware images for dsl routers
> (from a German company called AVM). 
> Although I couldn't find anything in the changelog the handling of hardlinks
> and some other types changed from 3.3 to 3.4. 

Handling of hardlinks and other types hasn't changed from 3.3 to 3.4.

> Actually we are using squashfs-3.3 which works perfectly but with 3.4 I get
> some errors: 
>  
> create_inode: could not create character device squashfs-root/dev/console,
> because you're not superuser! 
> create_inode: failed to create hardlink, because Bad address 
> create_inode: failed to create hardlink, because No such file or directory 

The code to determine if you're running unsquashfs as superuser hasn't 
changed from 3.3 to 3.4.  If fakeroot worked in 3.3 then it should work 
in 3.4.

>  
> And unsquashfs closes with a segmentation fault. We are doing unsquashfs in
> a fakeroot environment. Is there a switch to change this behaviour or can
> you give me a hint how to create soft-links instead of trying to create a
> hard-links? 

There's no changes in 3.4 that will cause the behaviour you're seeing. 
Additionally, Unsquashfs should never crash with a segmentation fault. 
I suspect you're hitting an unrelated bug which is causing memory 
corruption which is generating the above errors.

This unrelated bug is mostly likely in code that has changed from 3.3 to 
3.4, which is code to decompress regular files in parallel.  It is 
likely you have an unusual file which is triggering this bug.

Without a sample filesystem that causes these errors there's nothing I 
can do to track this down.  Can you send me a filesystem?

Thanks

Phillip

>  
> Regards 
> Oliver
> 
> Freetz - Open Source Fritz!Box Modding
> http://www.freetz.org
>