All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: b_lkasam@codeaurora.org
Cc: alsa-devel@alsa-project.org, lkasam@qti.qualcomm.com
Subject: Re: ALSA core info race condition
Date: Wed, 28 Jun 2017 07:36:17 +0200	[thread overview]
Message-ID: <s5hvangvfla.wl-tiwai@suse.de> (raw)
In-Reply-To: <70ff31e5f7fb35774cc0a9f3764ed144@codeaurora.org>

On Tue, 27 Jun 2017 21:12:18 +0200,
b_lkasam@codeaurora.org wrote:
> 
> hi ALSA team,
> there is a race condition in below API when accessing list API.
> 
> In file sound/core/info.c:
> 
> Added below patch to avoid list access of same parent node
> by two threads at same time causing list_debug crash.
> 
> diff --git a/sound/core/info.c b/sound/core/info.c
> index b5158b5..c1fd671 100644
> --- a/sound/core/info.c
> +++ b/sound/core/info.c
> @@ -747,8 +747,11 @@ snd_info_create_entry(const char *name, struct
> snd_info_entry *parent)
>  	INIT_LIST_HEAD(&entry->children);
>  	INIT_LIST_HEAD(&entry->list);
>  	entry->parent = parent;
> -	if (parent)
> +	if (parent) {
> +		mutex_lock(&parent->access);
>  		list_add_tail(&entry->list, &parent->children);
> +		mutex_unlock(&parent->access);
> +	}
>  	return entry;
>  }
> 
> Please check above logic looks fine, and help comment accordingly.

Have you ever got the actual crash?
The function is supposed to be called only at probing, and its link
base is the card object, so it's never called concurrently or the
concurrency should be managed in the caller side.

Your "fix" looks OK, but it's likely superfluous from the actual
usage.  Still it might be safer to add a protection, though.


thanks,

Takashi

  reply	other threads:[~2017-06-28  5:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27 19:12 ALSA core info race condition b_lkasam
2017-06-28  5:36 ` Takashi Iwai [this message]
2017-06-28  5:58   ` b_lkasam
2017-06-28  6:26     ` Takashi Iwai

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=s5hvangvfla.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=b_lkasam@codeaurora.org \
    --cc=lkasam@qti.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.