From: Takashi Iwai <tiwai@suse.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, LKML <linux-kernel@vger.kernel.org>,
Sasha Levin <sasha.levin@oracle.com>,
Alexander Potapenko <glider@google.com>,
Kostya Serebryany <kcc@google.com>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: sound: use-after-free in hrtimer_cancel
Date: Mon, 06 Jun 2016 16:11:05 +0200 [thread overview]
Message-ID: <s5hoa7emmpy.wl-tiwai@suse.de> (raw)
In-Reply-To: <CACT4Y+b1YEr5suLfUQVd_U+AU1fJ38DmGWbrLxaNay42-nAxYQ@mail.gmail.com>
On Sat, 04 Jun 2016 20:27:50 +0200,
Dmitry Vyukov wrote:
>
> On Sat, Jun 4, 2016 at 8:00 PM, Dmitry Vyukov <dvyukov@google.com> wrote:
> > Hello,
> >
> > The following program triggers use-after-free:
>
> Forget to mention that you need to run it in a tight parallel loop. It
> takes around 5 minutes to reproduce for me.
Hmm, this again is a bug that is difficult to trigger... At least, I
couldn't reproduce locally. How many processes are you running with
stress program?
It seems that there is nothing more than opening /dev/audio and does
some mmap in the job. Is there any other relevant thing there?
Also, this assumes that the first sound card is Dummy driver, right?
Check /proc/asound/cards.
If it's about snd-dummy driver, one blind shot would be a patch like
below. But even if it would fix, it doesn't explain why it's
triggered in that way...
thanks,
Takashi
---
diff --git a/sound/drivers/dummy.c b/sound/drivers/dummy.c
index c0f8f613f1f1..172dacd925f5 100644
--- a/sound/drivers/dummy.c
+++ b/sound/drivers/dummy.c
@@ -420,6 +420,7 @@ static int dummy_hrtimer_stop(struct snd_pcm_substream *substream)
static inline void dummy_hrtimer_sync(struct dummy_hrtimer_pcm *dpcm)
{
+ hrtimer_cancel(&dpcm->timer);
tasklet_kill(&dpcm->tasklet);
}
next prev parent reply other threads:[~2016-06-06 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 18:00 Dmitry Vyukov
2016-06-04 18:27 ` Dmitry Vyukov
2016-06-06 14:11 ` Takashi Iwai [this message]
2016-06-06 16:29 ` Dmitry Vyukov
2016-06-06 16:39 ` Takashi Iwai
2016-06-21 17:41 ` Dmitry Vyukov
2016-06-24 13:33 ` Takashi Iwai
2016-06-24 13:48 ` Dmitry Vyukov
2016-06-24 14:35 ` Takashi Iwai
2016-06-21 18:26 ` Dmitry Vyukov
2016-06-24 13:32 ` Takashi Iwai
2016-06-24 13:33 ` Dmitry Vyukov
2016-06-24 14:37 ` 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=s5hoa7emmpy.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.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®