From: Takashi Iwai <tiwai@suse.de>
To: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v2] ALSA: jack: Access input_dev under mutex
Date: Tue, 12 Apr 2022 11:44:14 +0200 [thread overview]
Message-ID: <s5hwnfuab69.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220412091628.3056922-1-amadeuszx.slawinski@linux.intel.com>
On Tue, 12 Apr 2022 11:16:28 +0200,
Amadeusz Sławiński wrote:
>
> It is possible when using ASoC that input_dev is unregistered while
> calling snd_jack_report, which causes NULL pointer dereference.
> In order to prevent this serialize access to input_dev using mutex lock.
>
> Signed-off-by: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
> ---
>
> Changes:
> v2:
> - drop mutex in snd_jack_new
> - add comment that snd_jack_report() should be called in context where
> it can sleep
Thanks, applied now.
Takashi
next prev parent reply other threads:[~2022-04-12 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 9:16 [PATCH v2] ALSA: jack: Access input_dev under mutex Amadeusz Sławiński
2022-04-12 9:44 ` Takashi Iwai [this message]
2022-04-12 10:07 ` Cezary Rojewski
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=s5hwnfuab69.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=cezary.rojewski@intel.com \
--cc=tiwai@suse.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