From: Jia-Ju Bai <baijiaju1990@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: keescook@chromium.org, perex@perex.cz,
alsa-devel@alsa-project.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] sound: pci: trident: a possible data race
Date: Thu, 4 Oct 2018 11:08:45 +0800 [thread overview]
Message-ID: <e334c065-5768-7710-bd70-059f7316157b@gmail.com> (raw)
In-Reply-To: <s5hk1mzowkd.wl-tiwai@suse.de>
Thanks for the reply :)
On 2018/10/3 23:54, Takashi Iwai wrote:
> On Wed, 03 Oct 2018 14:50:25 +0200,
> Jia-Ju Bai wrote:
>> CPU0:
>> snd_trident_hw_free
>> snd_trident_free_voice
>> line 3870: spin_lock_irqsave()
>> line 3881: voice->substream = NULL; [WRITE]
>> CPU1:
>> snd_trident_interrupt
>> line 3798: snd_pcm_period_elapsed(voice->substream); [READ]
>>
>> As for voice->substream, the WRITE operation in CPU0 is performed
>> with holding a spinlock, but the READ operation in CPU1 is performed
>> without holding this spinlock, so there may exist a data race.
> Thanks for the report.
>
> The actual crash must be very unlikely, almost 0%, though.
> snd_trident_hw_free() is called always after the PCM stream gets
> stopped via trigger callback, i.e. at the moment, there is no
> corresponding interrupt is generated for that voice entry.
How about the case that playback and capture are performed concurrently?
Namely, snd_trident_hw_free() is called for playback, and the interrupt
is generated for capture.
> And the hardware is very old, I bet only a handful people still using
> in the whole world :)
I have this hardware, so I am the one of these handful people ;)
Best wishes,
Jia-Ju Bai
next prev parent reply other threads:[~2018-10-04 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 12:50 [BUG] sound: pci: trident: a possible data race Jia-Ju Bai
2018-10-03 15:54 ` Takashi Iwai
2018-10-04 3:08 ` Jia-Ju Bai [this message]
2018-10-04 5:24 ` Takashi Iwai
2018-10-04 9:17 ` Jia-Ju Bai
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=e334c065-5768-7710-bd70-059f7316157b@gmail.com \
--to=baijiaju1990@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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