linux-kernel - Re: SquashFS on ARM9

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 07 Feb 2010 01:18:49 -0600
From:	Dick Hollenbeck <dick@...tplc.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: SquashFS on ARM9

Dick Hollenbeck wrote:
>
> Dear Philip et. al,
>
>
> I am using 2.6.30.5 on an ARM9 with squashfs.
>
> The squashFS image is built with x86_64 form of
>
>        mksquashfs version 4.1-CVS (2009/09/20)
>
> 64 bit linux program.
 >  There are no problems on the development system, only the ARM9.

OK I got more news:

The image works OK if I build it with the 32 version of mksquashs on x86.

Amazing, there are differences in file format other than endian-ness?

So we have at least 3 forms of the file system image now?  I am 
disappointed.  One would have sufficed.  I don't even buy the need for 
LSbyte vs MSbyte being needed.  There should have been only one form of 
the FS image.

Ouch, this seems amateurish.   Can I assume it is the bitfields?   Get 
rid of the bitfields!

Use #defines and OR and AND them please.

In the mksquashfs program, simply create some ints

(1<<a)
(1<<b)

etc using #defines.

Andrew Morton warned you about this years ago.  You have the bitfields 
using defines, its just that you control where the bits are:

#define MBIT (1<<2)

struct s {
    int32_t val;
} r;

r.val |= MBIT;

How hard is that really?

For now I don't need anymore help.  Sorry if I burned down my bridge, I 
only intend to offer strategy to improve the filesystem.

Dick

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/