Messages in this thread | | | Date | Mon, 23 Oct 2023 08:46:04 +0200 (CEST) | From | Richard Weinberger <> | Subject | Re: [PATCH v2] ubi: gluebi: Fix NULL pointer dereference caused by ftl notifier |
| |
----- Ursprüngliche Mail ----- > Von: "ZhaoLong Wang" <wangzhaolong1@huawei.com> > An: "richard" <richard@nod.at>, "chengzhihao1" <chengzhihao1@huawei.com> > CC: "Miquel Raynal" <miquel.raynal@bootlin.com>, "Vignesh Raghavendra" <vigneshr@ti.com>, "dpervushin" > <dpervushin@embeddedalley.com>, "Artem Bityutskiy" <Artem.Bityutskiy@nokia.com>, "linux-mtd" > <linux-mtd@lists.infradead.org>, "linux-kernel" <linux-kernel@vger.kernel.org>, "yi zhang" <yi.zhang@huawei.com>, > "yangerkun" <yangerkun@huawei.com> > Gesendet: Montag, 23. Oktober 2023 08:41:12 > Betreff: Re: [PATCH v2] ubi: gluebi: Fix NULL pointer dereference caused by ftl notifier
>> >> IOW, no mtdblock (hence, also no FTLs) on top of gluebi. >> >> What do you guys think? >> >> Thanks, >> //richard >> > > > JFFS2 needs to work on the block device, so the mtdblock needs to work > on the top of gluebi. > > This is directly reflected in the jffs2 mount command, such as > > # mount -t jffs2 /dev/mtdblockX /mnt/jffs2
The limitation is long gone. It comes from the dark and old times where Linux was only able to mount block devices.
You can do: mount -t jffs2 mtdX /mnt/jffs2
Thanks, //richard
| |