From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Mark Brown <broonie@kernel.org>, Dmitry Vyukov <dvyukov@google.com>
Cc: 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: Mon, 1 Feb 2016 22:43:02 +0900 [thread overview]
Message-ID: <56AF60E6.3050703@sakamocchi.jp> (raw)
In-Reply-To: <20160201122018.GC4455@sirena.org.uk>
On Feb 01 2016 21:20, Mark Brown wrote:
> On Mon, Feb 01, 2016 at 12:22:18PM +0100, Dmitry Vyukov wrote:
>> On Mon, Feb 1, 2016 at 12:16 PM, Mark Brown <broonie@kernel.org> wrote:
>
>>> 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.
>
> You should never rely on the output of get_maintainers without review,
> it's prone to both false positives and false negatives. Given that
> Sakamoto-san does not seem to appear in MAINTAINERS at all and you've
> not managed to find Liam who's a comaintainer for all the ASoC stuff I
> suspect you're doing this with --git enabled which is especially prone
> to false positives since it tends to identify people who are just doing
> global cleanup work and aren't particularly interested in a given file.
> As far as I can tell this is how I'm getting pulled in too rather than
> MAINTAINERS.
Aha. That's the reason I receive these messages. I've wondering why I
receive them.
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...
(Actually, Iwai-san posted patches to fix them at incredibly pace. I
can't follow his pace, because I'm working for ALSA in my free time.)
Regards
Takashi Sakamoto
prev parent reply other threads:[~2016-02-01 13:43 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 ` [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
2016-02-01 13:43 ` Takashi Sakamoto [this message]
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=56AF60E6.3050703@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox