linux-kernel - RE: [PATCH v6 01/11] mtd: core: always create master device

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: <CY5PR11MB63666AE267B9F1609213D93CED68A@CY5PR11MB6366.namprd11.prod.outlook.com>
Date: Sun, 8 Jun 2025 07:00:10 +0000
From: "Usyskin, Alexander" <alexander.usyskin@...el.com>
To: Guenter Roeck <linux@...ck-us.net>
CC: Miquel Raynal <miquel.raynal@...tlin.com>, Richard Weinberger
	<richard@....at>, Vignesh Raghavendra <vigneshr@...com>, "De Marchi, Lucas"
	<lucas.demarchi@...el.com>, Thomas Hellström
	<thomas.hellstrom@...ux.intel.com>, "Vivi, Rodrigo" <rodrigo.vivi@...el.com>,
	Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, Maxime Ripard
	<mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>, David Airlie
	<airlied@...il.com>, Simona Vetter <simona@...ll.ch>, Jani Nikula
	<jani.nikula@...ux.intel.com>, Joonas Lahtinen
	<joonas.lahtinen@...ux.intel.com>, Tvrtko Ursulin <tursulin@...ulin.net>,
	"Poosa, Karthik" <karthik.poosa@...el.com>, "Abliyev, Reuven"
	<reuven.abliyev@...el.com>, "Weil, Oren jer" <oren.jer.weil@...el.com>,
	"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v6 01/11] mtd: core: always create master device


> Subject: Re: [PATCH v6 01/11] mtd: core: always create master device
> 
> Hi,
> 
> On Sun, Mar 02, 2025 at 04:09:11PM +0200, Alexander Usyskin wrote:
> > Create master device without partition when
> > CONFIG_MTD_PARTITIONED_MASTER flag is unset.
> >
> > This streamlines device tree and allows to anchor
> > runtime power management on master device in all cases.
> >
> > Signed-off-by: Alexander Usyskin <alexander.usyskin@...el.com>
> 
> Several of my qemu boot tests fail to boot from mtd devices with this patch
> in the mainline kernel. Reverting it fixes the problem. As far as I can
> see this affects configurations with CONFIG_MTD_PARTITIONED_MASTER=y
> when
> trying to boot from an mtd partition other than mtdblock0, with the
> mtd partition data in devicetree (.../aspeed/openbmc-flash-layout.dtsi).
> Is there a guidance describing the changed behavior, by any chance,
> and how the boot command line now needs to look like when using one of
> the flash partitions as root file system ?
> 
> Thanks,
> Guenter

I've tried to make is as transparent as possible for the existing users.
Only change is that now every partition has master that is not partitioned.
Is the CONFIG_MTD_PARTITIONED_MASTER=n fixed the problem for you?

- - 
Thanks,
Sasha