From: "Michael Walle" <mwalle@kernel.org>
To: "Tze Yee Ng" <tze.yee.ng@altera.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Pratyush Yadav" <pratyush@kernel.org>,
"Takahiro Kuwano" <takahiro.kuwano@infineon.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v3 0/2] mtd: spi-nor: fix use-after-free on unbind with open handles
Date: Wed, 18 Nov 2026 10:36:20 +0100 [thread overview]
Message-ID: <DMY8H2AUQ3LV.VQ3MVOE3YV41@kernel.org> (raw)
In-Reply-To: <SJ0PR03MB5950FE5D82CA5E77AAE0AC9CA17A2@SJ0PR03MB5950.namprd03.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 425 bytes --]
Hi,
On Wed Nov 18, 2026 at 9:07 AM CET, Tze Yee Ng wrote:
> Gentle ping on this patch. Any chance for a review when you have time?
I had a quick glance, and honestly, I really don't like all the
reference and resource handling splattered all over the place. Also
do we really need the low level kref_ handling? And what about
spi-nand and all the other MTD subsystems? They have the same
problem, no?
-michael
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2026-11-18 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 3:53 [PATCH v3 0/2] mtd: spi-nor: fix use-after-free on unbind with open handles tze.yee.ng
2026-10-22 3:53 ` [PATCH v3 1/2] mtd: core: drop the module reference after ->_put_device() tze.yee.ng
2026-10-22 3:53 ` [PATCH v3 2/2] mtd: spi-nor: fix use-after-free on unbind with open handles tze.yee.ng
2026-10-22 4:18 ` sashiko-bot
2026-10-23 2:03 ` NG, TZE YEE
2026-11-03 3:53 ` NG, TZE YEE
[not found] ` <SJ0PR03MB5950FE5D82CA5E77AAE0AC9CA17A2@SJ0PR03MB5950.namprd03.prod.outlook.com>
2026-11-18 9:36 ` Michael Walle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DMY8H2AUQ3LV.VQ3MVOE3YV41@kernel.org \
--to=mwalle@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pratyush@kernel.org \
--cc=takahiro.kuwano@infineon.com \
--cc=tze.yee.ng@altera.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox