linux-kernel - Re: [PATCH for-4.11] ASoC: don't dereference NULL pcm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 14 Mar 2017 14:36:54 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Brian Norris <briannorris@...omium.org>
Cc:     Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org,
        Jaroslav Kysela <perex@...ex.cz>,
        Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
        Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org
Subject: Re: [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new,free}

On Mon, Mar 13, 2017 at 02:52:56PM -0700, Brian Norris wrote:

> Sure, I can understand frustration with essentially contentless "bug
> reports." And I got frustrated by a seemingly pat response that was
> (IMO) a bit mistargeted.

It *is* a pat response, it's one of the things I find I have to send
often enough that I've got a canned response for it - I find that if I
don't do things like that then after a while what gets sent becomes so
brief that unless you're really familiar with what's being said it can
be hard to understand the feedback.  It's tricky though because as you
say it's fairly obvious it's a form letter.

> BTW, I don't see the patch applied anywhere (and I have no reply -
> either manual or automated/patchwork - other than the above quote to say
> it was).

20170309102819.bx5paxtffvmvmuov@...ena.org.uk, fix/core  Didn't seem to
have made -next today, guess it'll hit tomorrow.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)