From: Guangshuo Li <liguangshuo@mail.sdu.edu.cn>
To: Lee Jones <lee@kernel.org>
Cc: Guangshuo Li <liguangshuo@mail.sdu.edu.cn>,
Support Opensource <support.opensource@diasemi.com>,
mfd@lists.linux.dev, linux-kernel@vger.kernel.org,
Manivannan Sadhasivam <mani@kernel.org>,
Cristian Ciocaltea <cristian.ciocaltea@gmail.com>,
linux-actions@lists.infradead.org,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
patches@opensource.cirrus.com
Subject: [PATCH 0/6] mfd: Fix potential cleanup ordering and lifetime bugs
Date: Sat, 31 Oct 2026 00:54:23 +0800 [thread overview]
Message-ID: <cover.1793377422.mfd.git.liguangshuo@mail.sdu.edu.cn> (raw)
Remove child devices while their IRQ providers are still available, and
avoid deleting a managed IRQ chip twice.
The changed driver objects were build-tested. No hardware testing was
performed.
Guangshuo Li (6):
mfd: da9055: Fix potential use-after-free during removal
mfd: atc260x: Fix potential use-after-free on probe failure
mfd: palmas: Fix potential IRQ action leaks on removal
mfd: stmpe: Fix potential use-after-free during removal
mfd: stmfx: Fix potential IRQ action leaks on removal
mfd: wm8994: Fix potential use-after-free during removal
drivers/mfd/atc260x-core.c | 4 +---
drivers/mfd/da9055-core.c | 2 +-
drivers/mfd/palmas.c | 3 +++
drivers/mfd/stmfx.c | 8 +++++---
drivers/mfd/stmpe.c | 4 ++--
drivers/mfd/wm8994-core.c | 7 +++++--
6 files changed, 17 insertions(+), 11 deletions(-)
base-commit: d89e1d186ec9271bf78e62771779e9fc03bf0fc3
next reply other threads:[~2026-10-30 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 16:54 Guangshuo Li [this message]
2026-10-30 16:54 ` [PATCH 1/6] mfd: da9055: Fix potential use-after-free during removal Guangshuo Li
2026-10-30 16:54 ` [PATCH 2/6] mfd: atc260x: Fix potential use-after-free on probe failure Guangshuo Li
2026-10-30 16:54 ` [PATCH 3/6] mfd: palmas: Fix potential IRQ action leaks on removal Guangshuo Li
2026-10-30 16:54 ` [PATCH 4/6] mfd: stmpe: Fix potential use-after-free during removal Guangshuo Li
2026-10-30 16:54 ` [PATCH 5/6] mfd: stmfx: Fix potential IRQ action leaks on removal Guangshuo Li
2026-10-30 16:54 ` [PATCH 6/6] mfd: wm8994: Fix potential use-after-free during removal Guangshuo Li
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=cover.1793377422.mfd.git.liguangshuo@mail.sdu.edu.cn \
--to=liguangshuo@mail.sdu.edu.cn \
--cc=aaro.koskinen@iki.fi \
--cc=alexandre.torgue@foss.st.com \
--cc=andreas@kemnade.info \
--cc=cristian.ciocaltea@gmail.com \
--cc=khilman@baylibre.com \
--cc=lee@kernel.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mani@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mfd@lists.linux.dev \
--cc=patches@opensource.cirrus.com \
--cc=rogerq@kernel.org \
--cc=support.opensource@diasemi.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®