All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Osterhoff <linux-kernel@k-raum.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: PATCH: ALSA: hda: fix possible null dereference
Date: Mon, 24 Aug 2015 12:17:40 +0200	[thread overview]
Message-ID: <20150824101740.GA13757@mo-online.de> (raw)
In-Reply-To: <s5hsi79ryfg.wl-tiwai@suse.de>

Dear Takashi,

maybe I am mistaken or have not made my patch clear, please let me
apologise.

* Takashi Iwai <tiwai@suse.de> [150824 08:30]:
> On Sun, 23 Aug 2015 20:37:05 +0200,
> Markus Osterhoff wrote:
> > With commits bbbc7e85 and 751e2216, a for-loop was restated using
> > list_for_each_entry(...); originally, a local pcm* was extracted from an array
> > and checked against NULL, if not-NULL then passed along to
> > snd_pcm_add_chmap_ctls(...).
> > 
> > For a history of the function in question, have a look at lines 2430ff for
> > 	git diff v4.0 v4.1 sound/pci/hda/hda_codec.c
> > 
> > The two commits that touched this function are
> > Commit bbbc7e8502c9 ("ALSA: hda - Allocate hda_pcm objects dynamically")
> > Commit 751e2216899c ("ALSA: hda: fix possible null dereference")
> > 
> > where the latter only fixes the order of two fixes, but not the pcm / pcm->pcm confusion.

> Thanks for the patch.  But this was already fixed by commit
> 751e2216899c in 4.1-rc1.
So I re-checked and diff'ed against the current v4.2-rc8 and found that
the if-statement reads, /sound/pci/hda/hda_codec.c, line 3172:
	if (!pcm || pcm->own_chmap ||
while I propose
	if (!pcm->pcm || pcm->own_chmap ||

With the mentioned 751e2216899c I do get a NULL dereference (for
whatever reason), because pcm->pcm can indeed by NULL inside the loop. Please
reconsider the patch:

> Takashi
Thanks for your time, Markus


Signed-off-by: Markus Osterhoff <linux-kernel@k-raum.org>
---
 sound/pci/hda/hda_codec.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/pci/hda/hda_codec.c b/sound/pci/hda/hda_codec.c
index 5de3c5d..47206b9 100644
--- a/sound/pci/hda/hda_codec.c
+++ b/sound/pci/hda/hda_codec.c
@@ -3172,7 +3172,7 @@ static int add_std_chmaps(struct hda_codec *codec)
                        struct snd_pcm_chmap *chmap;
                        const struct snd_pcm_chmap_elem *elem;
 
-                       if (!pcm || pcm->own_chmap ||
+                       if (!pcm->pcm || pcm->own_chmap ||
                            !hinfo->substreams)
                                continue;
                        elem = hinfo->chmap ? hinfo->chmap : snd_pcm_std_chmaps;

  reply	other threads:[~2015-08-24 10:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-23 18:37 PATCH: ALSA: hda: fix possible null dereference Markus Osterhoff
2015-08-24  6:30 ` Takashi Iwai
2015-08-24 10:17   ` Markus Osterhoff [this message]
2015-08-24 10:25     ` Takashi Iwai
2015-08-24 12:11       ` [PATCH RESEND V2] ALSA: hda: fix possible NULL dereference Markus Osterhoff
2015-08-24 13:04         ` 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=20150824101740.GA13757@mo-online.de \
    --to=linux-kernel@k-raum.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.