linux-kernel - Re: [PATCH] squashfs broken when pageszie

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: <49E3C209.5030705@lougher.demon.co.uk>
Date:	Mon, 13 Apr 2009 23:51:53 +0100
From:	Phillip Lougher <phillip@...gher.demon.co.uk>
To:	Doug Chapman <doug.chapman@...com>
CC:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] squashfs broken when pageszie > blocksize

Doug Chapman wrote:
> Squashfs is broken on any system where the pageszie is larger than either
> the block size of the squashfs image or larger than the metadata size (8192).
> This is easily fixed by ensuring cache->pages is always > 0.
> 
> Signed-off-by: Doug Chapman <doug.chapman@...com>
> Cc: Phillip Lougher <phillip@...gher.demon.co.uk>
> 

Good catch.  BTW what is the page size on ia64?

For completeness there should also be a mount time check that
the block size used in the Squashfs filesystem is at least as
large as the pagesize.  This doesn't matter for metadata
(size 8192), but does matter for data blocks, because Squashfs
read_page doesn't handle block_size < pagesize.

Squashfs read_page used to handle block_size < pagesize but I
removed that code when I removed filesystem support for block_sizes
< 4K.  If ia64 users (or any other architecture with larger than
4K pagesizes) want to use Squashfs filesystems with blocksizes less
than their pagesize, then I can put that code back in.

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/