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: <20131129132653.GA14204@amd.pavel.ucw.cz>
Date:	Fri, 29 Nov 2013 14:26:53 +0100
From:	Pavel Machek <pavel@....cz>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Peter Korsgaard <jacmet@...site.dk>,
	Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
	Richard Genoud <richard.genoud@...il.com>,
	zhouguangming@...ofidei.com,
	Hans Zhang <zhanghonghui@...ofidei.com>,
	linux-mtd <linux-mtd@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Make the mtdblock read/write skip the bad nand sector

Hi!

> > Hi,
> > 
> >  > Thanks a lot for the insight. After reading this, I'm wondering what's
> >  > preventing us from killing MTD block support altogether. Artem, already
> >  > suggested it a while back...
> > 
> > People using squashfs/cramfs/readonly ext2/.. on a NOR flash?
> 
> And people who *still*, after all these years, don't realise that they
> don't actually need it to mount JFFS2. Even as the root file system
> (although they *do* need rootfstype=jffs2).

I must admit I'm such person...

I guess printk("...you don't really need mtdblock...") in jffs2's
mount code would probably improve that realisation...

This certainly does not help:

pavel@amd:/data/l/linux-n900$ grep -ri mtdblock  Documentation
Documentation/frv/booting.txt:	   exec -c "console=ttySM0,115200
ip=:::::dhcp root=/dev/mtdblock2 rw"
Documentation/frv/booting.txt:	 /dev/mtdblock3	Fourth RedBoot
partition on the System Flash
Documentation/arm/SA1100/Assabet:which is the third one.  Within
Linux, this correspond to /dev/mtdblock2.
Documentation/arm/SA1100/Assabet:	exec -b 0x100000 -l 0xc0000 -c
"root=/dev/mtdblock2"

(Should not mtdblock be at least in devices.txt file?)

BTW... is there documentation of mtdblock "translation layer"
somewhere? I realize it is very simple, but it does need to keep some
data?

I guess running jffs on regular block device (USB stick, SD card) is
not feasible?
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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