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: <20141107200528.GA24946@ld-irv-0074>
Date:	Fri, 7 Nov 2014 12:05:28 -0800
From:	Brian Norris <computersforpeace@...il.com>
To:	Artem Bityutskiy <dedekind1@...il.com>
Cc:	Rodrigo Freire <rfreire@...hat.com>,
	Felix Fietkau <nbd@...nwrt.org>,
	Jörn Engel <joern@...fs.org>,
	Herton Krzesinski <hkrzesin@...hat.com>,
	linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org,
	dwmw2@...radead.org
Subject: Re: [RESEND PATCH V2] mtd: block2mtd: Present block2mtd timely on
 boot time

On Fri, Nov 07, 2014 at 11:44:40AM +0200, Artem Bityutskiy wrote:
> On Sat, 2014-11-01 at 09:33 -0400, Rodrigo Freire wrote:
> > From: Felix Fietkau <nbd@...nwrt.org> 
> > 
> > mtd: block2mtd: Ensure that block2mtd is presented timely on boot time
> > 
> > Currently, a block MTD device is not presented to the system on time, in 
> > order to start mounting the filesystems. This patch ensures that block2mtd 
> > is presented at the right time, so filesystems can be mounted on boot time. 
> > This issue is seen on BCM2835 (Raspberry Pi) systems when mounting JFFS2 
> > over block2mtd devices as the root filesystem.
> > This patchset also adds a MTD device name and a timeout option to the driver. 
> > Original patchset: 
> > https://dev.openwrt.org/browser/trunk/target/linux/generic/patches-3.12/440-block2mtd_init.patch?rev=40444 
> > https://dev.openwrt.org/browser/trunk/target/linux/generic/patches-3.12/441-block2mtd_probe.patch?rev=40444 
> 
> I  think you can mount jffs2 using /dev/mtdX, you do not need the block
> driver.

I realize you acknowledged your misunderstanding here, but for
posterity -- this point is addressed in the FAQ:

http://www.linux-mtd.infradead.org/faq/jffs2.html#L_mtdblock

Last I checked, the statement about busybox is still true. I think the
rootfs comment may be stale; I think the rootfstype= parameter can help
you.

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