From: Mark Brown <broonie@kernel.org>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: Dmitry Vyukov <dvyukov@google.com>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
Kostya Serebryany <kcc@google.com>,
syzkaller <syzkaller@googlegroups.com>,
Alexander Potapenko <glider@google.com>,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: sound: use-after-free in snd_seq_deliver_single_event
Date: Tue, 2 Feb 2016 19:26:03 +0000 [thread overview]
Message-ID: <20160202192603.GU4455@sirena.org.uk> (raw)
In-Reply-To: <56AF5EDF.9030202@sakamocchi.jp>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
On Mon, Feb 01, 2016 at 10:34:23PM +0900, Takashi Sakamoto wrote:
> Well, I don't mind to receive them because it's a good information for
> me to get current state of ALSA core functionality. If I had some
> spare time, I was also going to fix it. But currently I have little
> time for it due to my development for my minor hardwares...
Yeah, my concern is that I'm getting to the point where I mentally tag
them as irrelevant and delete them unread (the subject lines don't help
here). I've had quite a few and none of them have been for code I even
recall working on.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-02-02 19:26 UTC|newest]
Thread overview: 12+ 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 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 ` [alsa-devel] " Takashi Iwai
2016-02-01 12:20 ` Mark Brown
2016-02-01 13:34 ` Takashi Sakamoto
2016-02-02 19:26 ` Mark Brown [this message]
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=20160202192603.GU4455@sirena.org.uk \
--to=broonie@kernel.org \
--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=o-takashi@sakamocchi.jp \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.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 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.