From: Takashi Iwai <tiwai@suse.de>
To: Wang YanQing <udknight@gmail.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
perex@perex.cz, david.henningsson@canonical.com
Subject: Re: [PATCH]ALSA: HDA: Fix Oops caused by dereference NULL pointer
Date: Tue, 07 May 2013 07:34:59 +0200 [thread overview]
Message-ID: <s5hip2v1hfg.wl%tiwai@suse.de> (raw)
In-Reply-To: <20130507032733.GA29944@udknight>
At Tue, 7 May 2013 11:27:33 +0800,
Wang YanQing wrote:
>
> The interrupt handler azx_interrupt will call azx_update_rirb,
> which may call snd_hda_queue_unsol_event, snd_hda_queue_unsol_event
> will dereference chip->bus pointer.
>
> The problem is we alloc chip->bus in azx_codec_create
> which will be called after we enable IRQ and enable unsolicited
> event in azx_probe.
>
> This will cause Oops due dereference NULL pointer. I meet it, good luck:)
>
> Signed-off-by: Wang YanQing <udknight@gmail.com>
Thanks, applied with a slight fix (put before the tracepoint so that
it won't give more NULL dereference, and also put another NULL check
of bus->workq as done in hda_intel.c.)
Takashi
> ---
> sound/pci/hda/hda_codec.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/sound/pci/hda/hda_codec.c b/sound/pci/hda/hda_codec.c
> index 622f726..9c76752 100644
> --- a/sound/pci/hda/hda_codec.c
> +++ b/sound/pci/hda/hda_codec.c
> @@ -618,6 +618,9 @@ int snd_hda_queue_unsol_event(struct hda_bus *bus, u32 res, u32 res_ex)
> unsigned int wp;
>
> trace_hda_unsol_event(bus, res, res_ex);
> + if (!bus)
> + return 0;
> +
> unsol = bus->unsol;
> if (!unsol)
> return 0;
> --
> 1.7.12.4.dirty
>
prev parent reply other threads:[~2013-05-07 5:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 3:27 [PATCH]ALSA: HDA: Fix Oops caused by dereference NULL pointer Wang YanQing
2013-05-07 5:34 ` Takashi Iwai [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=s5hip2v1hfg.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=udknight@gmail.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