linux-kernel - CRAMFS support for 4KB page NAND FLASH

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>] [day] [month] [year] [list]

Message-ID: <6334E09627481B4AA5C8DE1E69E19D3B06BF98AD@SSLEXCHANGE.solomonsystech.com>
Date:	Thu, 5 Jul 2007 11:51:46 +0800
From:	<sasin@...omon-systech.com>
To:	<linux-kernel@...r.kernel.org>
Subject: CRAMFS support for 4KB page NAND FLASH

Trying to boot off CRAMFS on a 4KB page NAND FLASH (new device), I ran
into the "wrong magic" issue.  MTD's nand_read
(drivers/mtd/nand/nand_base.c) is returning the right data.
cramfs_fill_supper calls cramfs_read (fs/cramfs/inode.c) which reads 4
pages and the 1st page of data gets corrupted.  If I set
BLKS_PER_BUF_SHIFT in this file to 0 instead of 2, so that only 1 page
is read, the data is uncorrupted and the magic value matches but it
crashes later (comments say that this values should be 2 or higher, so
this is not surprising).  

So are 4KB-page devices supported by CRAMFS?

I'm using linux 2.6.20.1 for ARM. 
-
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/