From: Manish Baing <manishbaing2789@gmail•com>
To: perex@perex•cz, tiwai@suse•com, nicolas.ferre@microchip•com,
alexandre.belloni@bootlin•com, claudiu.beznea@tuxon•dev
Cc: linux-sound@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org, manishbaing2789@gmail•com
Subject: [RFC PATCH 0/2] ASoC: atmel: ac97c: Fix IRQ handling sequences
Date: Thu, 4 Jun 2026 20:36:21 +0000 [thread overview]
Message-ID: <20260604203623.162640-1-manishbaing2789@gmail.com> (raw)
This series addresses two hardware initialization and teardown issues in
the atmel_ac97c driver flagged by the Sashiko AI bot.
The original report can be found here:
https://sashiko.dev/#/patchset/20260530052812.115994-1-manishbaing2789@gmail.com?part=1
- Patch 1 moves request_irq() to the end of probe to prevent a null pointer
dereference if an interrupt fires early.
- Patch 2 reorders the teardown sequence to free the IRQ before disabling
clocks and unmapping memory, preventing a use-after-free.
I am submitting this as an RFC because I do not have the physical hardware
to test these changes, However, my manual analysis indicates these are
valid bugs, and the series compiles cleanly with W=1.
Manish Baing (2):
ASoC: sound: atmel_ac97c: Fix IRQ handler null pointer dereference
ASoC: atmel: ac97c: Fix use-after-free on driver teardown
sound/atmel/ac97c.c | 20 +++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2026-06-04 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 20:36 Manish Baing [this message]
2026-06-04 20:36 ` [RFC PATCH 1/2] ASoC: sound: atmel_ac97c: Fix IRQ handler null pointer dereference Manish Baing
2026-06-04 20:36 ` [RFC PATCH 2/2] ASoC: atmel: ac97c: Fix use-after-free on driver teardown Manish Baing
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=20260604203623.162640-1-manishbaing2789@gmail.com \
--to=manishbaing2789@gmail$(echo .)com \
--cc=alexandre.belloni@bootlin$(echo .)com \
--cc=claudiu.beznea@tuxon$(echo .)dev \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-sound@vger$(echo .)kernel.org \
--cc=nicolas.ferre@microchip$(echo .)com \
--cc=perex@perex$(echo .)cz \
--cc=tiwai@suse$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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