From: Qais Yousef <qais.yousef@imgtec.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Vinod Koul <vinod.koul@intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: ASoC: soc-compress.c: fix NULL dereference
Date: Fri, 2 Jan 2015 09:07:32 +0000 [thread overview]
Message-ID: <54A65FD4.10600@imgtec.com> (raw)
In-Reply-To: <20141229161303.GU17800@sirena.org.uk>
On 12/29/2014 04:13 PM, Mark Brown wrote:
> On Tue, Dec 23, 2014 at 09:09:27AM +0000, Qais Yousef wrote:
>> In soc_new_compress() when rtd->dai_link->daynmic is set, we create the pcm
>> substreams with this call:
>>
>> ret = snd_pcm_new_internal(rtd->card->snd_card, new_name, num,
>> 1, 0, &be_pcm);
>>
>> which passes 0 as capture_count leading to
>>
>> be_pcm->streams[SNDRV_PCM_STREAM_CAPTURE].substream
>>
>> being NULL, hence when trying to set rtd a few lines below we get an oops.
>> Fix by removing this line of code since CAPTURE substream will always be NULL.
> Why will the capture stream always be NULL? There should be no
> intrinsic reason why we can't have hardware support for capturing
> compressed audio.
I think because we pass 0 as capture_count in snd_pcm_new_internal(). If
I read the code correctly this will lead to _snd_pcm_new() to be called
which in return will call snd_pcm_new_stream(pcm,
SNDRV_PCM_STREAM_CAPTURE, capture_count) which will cause no substream
to be allocated for the capture case, hence being NULL. I get an oops in
my experimental driver when I set dynamic = 1 in FE dai link. If I did
something wrong there that caused this, it's not obvious to me how.
Maybe a better fix would be to replace the 1 and 0 in
snd_pcm_new_internal() call with rtd->dai_link->dpcm_playback and
rtd->dai_link->dpcm_capture.
WARNING: multiple messages have this Message-ID (diff)
From: Qais Yousef <qais.yousef@imgtec.com>
To: Mark Brown <broonie@kernel.org>
Cc: <alsa-devel@alsa-project.org>, Vinod Koul <vinod.koul@intel.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, "Takashi Iwai" <tiwai@suse.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: ASoC: soc-compress.c: fix NULL dereference
Date: Fri, 2 Jan 2015 09:07:32 +0000 [thread overview]
Message-ID: <54A65FD4.10600@imgtec.com> (raw)
In-Reply-To: <20141229161303.GU17800@sirena.org.uk>
On 12/29/2014 04:13 PM, Mark Brown wrote:
> On Tue, Dec 23, 2014 at 09:09:27AM +0000, Qais Yousef wrote:
>> In soc_new_compress() when rtd->dai_link->daynmic is set, we create the pcm
>> substreams with this call:
>>
>> ret = snd_pcm_new_internal(rtd->card->snd_card, new_name, num,
>> 1, 0, &be_pcm);
>>
>> which passes 0 as capture_count leading to
>>
>> be_pcm->streams[SNDRV_PCM_STREAM_CAPTURE].substream
>>
>> being NULL, hence when trying to set rtd a few lines below we get an oops.
>> Fix by removing this line of code since CAPTURE substream will always be NULL.
> Why will the capture stream always be NULL? There should be no
> intrinsic reason why we can't have hardware support for capturing
> compressed audio.
I think because we pass 0 as capture_count in snd_pcm_new_internal(). If
I read the code correctly this will lead to _snd_pcm_new() to be called
which in return will call snd_pcm_new_stream(pcm,
SNDRV_PCM_STREAM_CAPTURE, capture_count) which will cause no substream
to be allocated for the capture case, hence being NULL. I get an oops in
my experimental driver when I set dynamic = 1 in FE dai link. If I did
something wrong there that caused this, it's not obvious to me how.
Maybe a better fix would be to replace the 1 and 0 in
snd_pcm_new_internal() call with rtd->dai_link->dpcm_playback and
rtd->dai_link->dpcm_capture.
next prev parent reply other threads:[~2015-01-02 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 9:09 [PATCH] ALSA: ASoC: soc-compress.c: fix NULL dereference Qais Yousef
2014-12-23 9:09 ` Qais Yousef
2014-12-29 16:13 ` Mark Brown
2015-01-02 9:07 ` Qais Yousef [this message]
2015-01-02 9:07 ` Qais Yousef
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=54A65FD4.10600@imgtec.com \
--to=qais.yousef@imgtec.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.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.