From: Takashi Iwai <tiwai@suse.de>
To: Xiaoke Wang <xkernel.wang@foxmail.com>
Cc: perex@perex.cz, tiwai@suse.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: sound/isa/gus: check the return value of kstrdup()
Date: Mon, 13 Dec 2021 10:54:00 +0100 [thread overview]
Message-ID: <s5hilvsesp3.wl-tiwai@suse.de> (raw)
In-Reply-To: <tencent_62C8C2B79490FE8D4000985D724D38842809@qq.com>
On Mon, 13 Dec 2021 09:06:47 +0100,
Xiaoke Wang wrote:
>
> Note: Compare with the last email, this one is using my full name.
> kstrdup() returns NULL when some internal memory errors happen, it is
> better to check the return value of it. Otherwise, we may not to be able
> to catch some memory errors in time.
>
> Signed-off-by: Xiaoke Wang <xkernel.wang@foxmail.com>
The patch again forgot about the proper error handling...
This will leave the mutex unbalanced.
Please be careful when writing this kind of fix at the next time.
Many code paths require the proper error handling, e.g. freeing the
rest memory or unlock/lock something.
In this particular case, snd_gf1_mem_lock(alloc, 1) is needed at the
first chunk.
And, the easiest way to fix would be to have a NULL check in
snd_gf1_mem_xalloc(). Then that will cover all callers by once.
thanks,
Takashi
> ---
> sound/isa/gus/gus_mem.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/sound/isa/gus/gus_mem.c b/sound/isa/gus/gus_mem.c
> index ff9480f..f8d915f 100644
> --- a/sound/isa/gus/gus_mem.c
> +++ b/sound/isa/gus/gus_mem.c
> @@ -199,6 +199,8 @@ struct snd_gf1_mem_block *snd_gf1_mem_alloc(struct snd_gf1_mem * alloc, int owne
> memcpy(&block.share_id, share_id, sizeof(block.share_id));
> block.owner = owner;
> block.name = kstrdup(name, GFP_KERNEL);
> + if (block.name == NULL)
> + return NULL;
> nblock = snd_gf1_mem_xalloc(alloc, &block);
> snd_gf1_mem_lock(alloc, 1);
> return nblock;
> @@ -237,13 +239,13 @@ int snd_gf1_mem_init(struct snd_gus_card * gus)
> block.ptr = 0;
> block.size = 1024;
> block.name = kstrdup("InterWave LFOs", GFP_KERNEL);
> - if (snd_gf1_mem_xalloc(alloc, &block) == NULL)
> + if (block.name == NULL || snd_gf1_mem_xalloc(alloc, &block) == NULL)
> return -ENOMEM;
> }
> block.ptr = gus->gf1.default_voice_address;
> block.size = 4;
> block.name = kstrdup("Voice default (NULL's)", GFP_KERNEL);
> - if (snd_gf1_mem_xalloc(alloc, &block) == NULL)
> + if (block.name == NULL || snd_gf1_mem_xalloc(alloc, &block) == NULL)
> return -ENOMEM;
> #ifdef CONFIG_SND_DEBUG
> snd_card_ro_proc_new(gus->card, "gusmem", gus, snd_gf1_mem_info_read);
> --
>
next prev parent reply other threads:[~2021-12-13 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 8:06 Xiaoke Wang
2021-12-13 9:54 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-12 16:13 xkernel
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=s5hilvsesp3.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=xkernel.wang@foxmail.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®