[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <561660214.251562.1718638970757.JavaMail.zimbra@nod.at>
Date: Mon, 17 Jun 2024 17:42:50 +0200 (CEST)
From: Richard Weinberger <richard@....at>
To: Gagan Sidhu <broly@....com>
Cc: ZhaoLong Wang <wangzhaolong1@...wei.com>,
Artem Bityutskiy <Artem.Bityutskiy@...ia.com>,
chengzhihao1 <chengzhihao1@...wei.com>,
dpervushin <dpervushin@...eddedalley.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-mtd <linux-mtd@...ts.infradead.org>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Vignesh Raghavendra <vigneshr@...com>,
yangerkun <yangerkun@...wei.com>, yi zhang <yi.zhang@...wei.com>
Subject: Re: [PATCH v2] ubi: gluebi: Fix NULL pointer dereference caused by
ftl notifier
----- Ursprüngliche Mail -----
> Von: "Gagan Sidhu" <broly@....com>
> typically what happens is we will wrap a squashfs filesystem inside a UBI layer.
> openwrt people call this “ubinising” the root filesystem.
>
> then, after we label the appropriate nand partitions as ‘uimage,fw’ to call the
> right mtdsplit, the mtd_ubi subsystem works its magic automatically, as long as
> the root partition is named “rootfs”.
>
> at that point, the rootfs will be *AUTOMATICALLY* mounted AND booted from BY THE
> KERNEL. that is, no cmdline hacks are required.
>
> this patch breaks that behaviour since mr wang’s additional conditions result in
> the failure of the partition to get added to the mtd list, and thus fails
> mount.
>
Please help me understanding the layering.
So, you have sqaushfs inside an UBI volume and create a UBI block device from that?
And you have enabled gluebi to have the said UBI volume as MTD (and thus as mtdblock too)?
Thanks,
//richard
Powered by blists - more mailing lists