From: Takashi Iwai <tiwai@suse.de>
To: linux-sound@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 32/32] ALSA: Drop unused snd_card_free_on_error()
Date: Thu, 1 Oct 2026 13:04:12 +0200 [thread overview]
Message-ID: <20261001110447.486782-33-tiwai@suse.de> (raw)
In-Reply-To: <20261001110447.486782-1-tiwai@suse.de>
Now that all users of snd_card_free_on_error() are gone by refactoring
with auto-cleanup, let's drop the superfluous function.
Also, update the documentation for reflecting the recommended error
handling procedure, too.
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
include/sound/core.h | 1 -
sound/core/init.c | 36 +++++++-----------------------------
2 files changed, 7 insertions(+), 30 deletions(-)
diff --git a/include/sound/core.h b/include/sound/core.h
index 2ca24ac7e37f..dc356e1ff47a 100644
--- a/include/sound/core.h
+++ b/include/sound/core.h
@@ -314,7 +314,6 @@ void snd_card_disconnect(struct snd_card *card);
void snd_card_disconnect_sync(struct snd_card *card);
void snd_card_free(struct snd_card *card);
void snd_card_free_when_closed(struct snd_card *card);
-int snd_card_free_on_error(struct device *dev, int ret);
void snd_card_set_id(struct snd_card *card, const char *id);
int snd_card_register(struct snd_card *card);
int snd_card_info_init(void);
diff --git a/sound/core/init.c b/sound/core/init.c
index a51b71812fd9..0897b3a11617 100644
--- a/sound/core/init.c
+++ b/sound/core/init.c
@@ -216,11 +216,13 @@ static void __snd_card_release(struct device *dev, void *data)
* is added automatically. In that way, the resource disconnection is assured
* at first, then released in the expected order.
*
- * If an error happens at the probe before snd_card_register() is called and
- * there have been other devres resources, you'd need to free the card manually
- * via snd_card_free() call in the error; otherwise it may lead to UAF due to
- * devres call orders. You can use snd_card_free_on_error() helper for
- * handling it more easily.
+ * Caveat: if an error happens at the probe before snd_card_register() is
+ * called and there have been other devres resources that are referred at the
+ * card-level destructor call, you'd still need to free the card manually;
+ * otherwise it may lead to UAF due to devres call orders. Instead of a manual
+ * snd_card_free() call, you can use the automatic clean-up for the card
+ * pointer via __free(snd_card_unref), and clear it upon the successful return,
+ * too; the snd_card_unref() would work just like snd_card_free() in this case.
*
* Return: zero if successful, or a negative error code
*/
@@ -250,30 +252,6 @@ int snd_devm_card_new(struct device *parent, int idx, const char *xid,
}
EXPORT_SYMBOL_GPL(snd_devm_card_new);
-/**
- * snd_card_free_on_error - a small helper for handling devm probe errors
- * @dev: the managed device object
- * @ret: the return code from the probe callback
- *
- * This function handles the explicit snd_card_free() call at the error from
- * the probe callback. It's just a small helper for simplifying the error
- * handling with the managed devices.
- *
- * Return: zero if successful, or a negative error code
- */
-int snd_card_free_on_error(struct device *dev, int ret)
-{
- struct snd_card *card;
-
- if (!ret)
- return 0;
- card = devres_find(dev, __snd_card_release, NULL, NULL);
- if (card)
- snd_card_free(card);
- return ret;
-}
-EXPORT_SYMBOL_GPL(snd_card_free_on_error);
-
static int snd_card_init(struct snd_card *card, struct device *parent,
int idx, const char *xid, struct module *module,
size_t extra_size)
--
2.55.0
prev parent reply other threads:[~2026-10-01 11:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 11:03 [PATCH 00/32] ALSA: Use auto-cleanup for probe card error handling Takashi Iwai
2026-10-01 11:03 ` [PATCH 01/32] ALSA: galaxy: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 02/32] ALSA: sc6000: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 03/32] ALSA: ad1889: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 04/32] ALSA: ali5451: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 05/32] ALSA: als4000: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 06/32] ALSA: atiixp: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 07/32] ALSA: au88x0: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 08/32] ALSA: azt3328: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 09/32] ALSA: bt87x: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 10/32] ALSA: ca0106: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 11/32] ALSA: cs4281: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 12/32] ALSA: cs5535audio: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 13/32] ALSA: echoaudio: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 14/32] ALSA: emu10k1x: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 15/32] ALSA: ens137x: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 16/32] ALSA: es1938: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 17/32] ALSA: es1968: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 18/32] ALSA: fm801: " Takashi Iwai
2026-10-01 11:03 ` [PATCH 19/32] ALSA: ice1724: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 20/32] ALSA: intel8x0: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 21/32] ALSA: lola: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 22/32] ALSA: maestro3: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 23/32] ALSA: oxygen: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 24/32] ALSA: riptide: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 25/32] ALSA: rme32: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 26/32] ALSA: rm96: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 27/32] ALSA: sis7019: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 28/32] ALSA: sonicbibes: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 29/32] ALSA: via82xx: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 30/32] ALSA: ymfpci: " Takashi Iwai
2026-10-01 11:04 ` [PATCH 31/32] ALSA: intel-hdmi-audio: " Takashi Iwai
2026-10-01 11:04 ` Takashi Iwai [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=20261001110447.486782-33-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
/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®