From: Takashi Iwai <tiwai@suse.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org, LKML <linux-kernel@vger.kernel.org>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Kostya Serebryany <kcc@google.com>,
syzkaller <syzkaller@googlegroups.com>,
Alexander Potapenko <glider@google.com>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: [alsa-devel] sound: use-after-free in snd_seq_deliver_single_event
Date: Mon, 01 Feb 2016 13:03:16 +0100 [thread overview]
Message-ID: <s5hvb68myd7.wl-tiwai@suse.de> (raw)
In-Reply-To: <CACT4Y+YXXYWUGSZ5y=ZHPJXVAKXeEXLn8vjkpm+xx98yfo4dxw@mail.gmail.com>
On Mon, 01 Feb 2016 12:22:18 +0100,
Dmitry Vyukov wrote:
>
> On Mon, Feb 1, 2016 at 12:16 PM, Mark Brown <broonie@kernel.org> wrote:
> > On Mon, Feb 01, 2016 at 11:26:57AM +0100, Dmitry Vyukov wrote:
> >
> >> The following program triggers use-after-free in
> >> snd_seq_deliver_single_event (run in a tight parallel loop):
> >
> > I'm not sure how you're working out who to send these to but all these
> > reports you've been sending have been for ALSA core which I rarely look
> > at closely, I mostly look at ASoC. Might be worth looking into so
> > people don't start zoning out things that look like misdirected stuff
> > (I just noticed myself doing that with this).
>
>
> I am using scripts/get_maintainer.pl -f the involved files. If it
> produces wrong results, please update MAINTAINERS.
Well, MAINTAINERS file points that Mark is responsible for
sound/soc/*, but not for sound/* in general.
Takashi
next prev parent reply other threads:[~2016-02-01 12:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 10:26 sound: use-after-free in snd_seq_deliver_single_event Dmitry Vyukov
2016-02-01 10:57 ` Takashi Iwai
2016-02-01 11:12 ` Dmitry Vyukov
2016-02-01 11:29 ` Takashi Iwai
2016-02-01 11:16 ` Mark Brown
2016-02-01 11:22 ` Dmitry Vyukov
2016-02-01 12:03 ` Takashi Iwai [this message]
2016-02-01 12:20 ` Mark Brown
2016-02-01 13:34 ` Takashi Sakamoto
2016-02-02 19:26 ` Mark Brown
2016-02-01 13:43 ` Takashi Sakamoto
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=s5hvb68myd7.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--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