linux-kernel - Re: [PATCH v3 1/1] mtd: spi-nor: core: Prevent oops during driver removal with active read or write 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>] [day] [month] [year] [list]

Message-Id: <DC7WIIFZQ448.3RW1U45I41129@kernel.org>
Date: Thu, 21 Aug 2025 08:44:57 +0200
From: "Michael Walle" <mwalle@...nel.org>
To: "Romli, Khairul Anuar" <khairul.anuar.romli@...era.com>, "Tudor Ambarus"
 <tudor.ambarus@...aro.org>, "Pratyush Yadav" <pratyush@...nel.org>, "Miquel
 Raynal" <miquel.raynal@...tlin.com>, "Richard Weinberger" <richard@....at>,
 "Vignesh Raghavendra" <vigneshr@...com>, "open list:SPI NOR SUBSYSTEM"
 <linux-mtd@...ts.infradead.org>, "open list"
 <linux-kernel@...r.kernel.org>, "Gerlach, Matthew"
 <matthew.gerlach@...era.com>
Subject: Re: [PATCH v3 1/1] mtd: spi-nor: core: Prevent oops during driver
 removal with active read or write operations

Hi,

On Thu Aug 21, 2025 at 2:32 AM CEST, Khairul Anuar Romli wrote:
> Sorry for taking very long time to reply. Could you advise me what
> kind of analysis do you want me to provide?

Please don't top-post, see [1]. An explanation what is going wrong
and why (and no, a backtrace is not an explanation). Why is
dev->driver->owner NULL? Shouldn't it be guarded by a lock or
something? And esp. why is owner NULL in put_device().

-michael

>
> > -----Original Message-----
> > From: Michael Walle <mwalle@...nel.org>
> > Sent: Wednesday, 30 July, 2025 3:50 PM
> > To: Romli, Khairul Anuar <khairul.anuar.romli@...era.com>; Tudor Ambarus
> > <tudor.ambarus@...aro.org>; Pratyush Yadav <pratyush@...nel.org>; Miquel
> > Raynal <miquel.raynal@...tlin.com>; Richard Weinberger <richard@....at>;
> > Vignesh Raghavendra <vigneshr@...com>; open list:SPI NOR SUBSYSTEM
> > <linux-mtd@...ts.infradead.org>; open list <linux-kernel@...r.kernel.org>;
> > Gerlach, Matthew <matthew.gerlach@...era.com>
> > Subject: Re: [PATCH v3 1/1] mtd: spi-nor: core: Prevent oops during driver
> > removal with active read or write operations
> > 
> > Hi,
> > 
> > > > On Wed Jul 30, 2025 at 3:39 AM CEST, Khairul Anuar Romli wrote:
> > > > > From: kromli <khairul.anuar.romli@...era.com>
> > > > >
> > > > > Ensure that the pointer passed to module_put() in
> > > > > spi_nor_put_device() is not NULL before use. This change adds a
> > > > > guard clause to return early, preventing the kernel crash below
> > > > > when the cadence-qspi driver is removed during a dd operation:
> > > >
> > > > As already asked in v2. This needs a (more detailed) description
> > > > what is going on and what is going wrong.
> > > >
> > > > -michael
> > >
> > > Hi,
> > >
> > > We just run the following test we observe the crash.
> > >
> > > time dd if=/dev/mtd1 of=out.img bs=1MB count=1000 & echo spi0.0 >
> > > /sys/bus/spi/drivers/spi-nor/unbind
> > > echo spi0.0 > /sys/bus/spi/drivers/spi-nor/bind
> > >
> > > From the observation, the dd is not entirely terminated when the unbind
> > took place.
> > > Maybe there is other changes require to ensure the dd operation gets
> > > terminated when driver unbind/remove.
> > 
> > I'd expect an analysis what's going wrong in the kernel to judge the correctness
> > of the patch.
> > 
> > Thanks,
> > -michael

[1] https://subspace.kernel.org/etiquette.html

Download attachment "signature.asc" of type "application/pgp-signature" (298 bytes)