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]
Message-ID: <cce9e37e1002070552h6514ecf5u634b184e4928a009@mail.gmail.com>
Date:	Sun, 7 Feb 2010 13:52:23 +0000
From:	Phillip Lougher <phil.lougher@...il.com>
To:	Dick Hollenbeck <dick@...tplc.com>
Cc:	linux-kernel@...r.kernel.org,
	Phillip Lougher <phillip@...gher.demon.co.uk>
Subject: Re: SquashFS on ARM9

On Sun, Feb 7, 2010 at 7:18 AM, Dick Hollenbeck <dick@...tplc.com> wrote:
> Dick Hollenbeck wrote:

> The image works OK if I build it with the 32 version of mksquashs on x86 vs x86_64 .
>
> Amazing, there are differences in file format other than endian-ness?

If you've found a difference in filesystems built by mksquashfs on x86
vs x86_64, then it is a *bug*.

>
> 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!
>

No need for insults, especially as it is based on an outdated
understanding.  Squashfs became fixed endian, and lost the bit-fields
in Squashfs 4.0.

> 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.
>

I like constructive feedback, excessively critical feedback is usually
self-defeating as it generally gets ignored.  By saying "Sorry if I
burned down my bridge" means you obviously understand this, and so it
is weird you bothered to send the email.

If you'd like the bug tracked down please raise it on the
squashfs.sourceforge.net bug tracker.  Include as much information as
you can including distribution, architecture, Mksquashfs options etc.
It would be best if you can provide a testcase set of source
directories that generate differing Squashfs filesystems on
x86/x86_64.

Phillip
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ