linux-kernel - RE: [PATCH v3 06/10] mtd: intel-dg: wake card on operations

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: <CY5PR11MB63663D73FA8ED331F8229AA1ED082@CY5PR11MB6366.namprd11.prod.outlook.com>
Date: Sun, 29 Dec 2024 15:08:56 +0000
From: "Usyskin, Alexander" <alexander.usyskin@...el.com>
To: Miquel Raynal <miquel.raynal@...tlin.com>, "Vivi, Rodrigo"
	<rodrigo.vivi@...el.com>, "Poosa, Karthik" <karthik.poosa@...el.com>, "De
 Marchi, Lucas" <lucas.demarchi@...el.com>
CC: Richard Weinberger <richard@....at>, Vignesh Raghavendra
	<vigneshr@...com>, Thomas Hellström
	<thomas.hellstrom@...ux.intel.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>, "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 v3 06/10] mtd: intel-dg: wake card on operations

> 
> Hello Alexander,
> 
> >> If so, I have to add patch for mtd subsystem to always have device for
> master
> >> initialized regardless of kernel flag.
> >> Only to initialize struct device, not to create full mtd node.
> >>
> >> Miquel - are you agree to this?
> 
> Conceptually yes, but please mind one thing: we do not break
> userspace. So if you want to keep the master mtd device, fine, but you
> need to do it in a consistent way so that people not enabling the kernel
> flag won't get a new device in their rootfs, shifting all indexes
> upwards.
> 
> That being said, you are probably going in the right direction by doing
> that.
> 
> Thanks,
> Miquèl

I've looked into this endeavour and seemed that there a need for special
device class and careful attention in release flow to use right class.
It will take time to do right.
Miquel, Rodrigo, Karthik, Lucas - may the DG NVM code be merged in the current
form and this device be added later?

- - 
Thanks,
Sasha