From: Wu Fengguang <fengguang.wu@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Guo, Chaohong" <chaohong.guo@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
John Villalovos <jvillalo@redhat.com>
Subject: Re: [PATCH] hda: add bounds checking for the codec command fields v2
Date: Fri, 17 Jul 2009 19:05:52 +0800 [thread overview]
Message-ID: <20090717110552.GA21516@localhost> (raw)
In-Reply-To: <s5hljmn8u52.wl%tiwai@suse.de>
On Fri, Jul 17, 2009 at 06:46:01PM +0800, Takashi Iwai wrote:
> At Fri, 17 Jul 2009 18:41:05 +0800,
> Guo, Chaohong wrote:
> >
> > Although it does address this issue, I am not comfortable with this fixing.
> > It seems more like a workaround than fix.
>
> No, it's rather for catching a bug. This is definitely neither
> "workaround" nor "fix".
Yes, I wrote this mainly for catching unknown bugs.
> > Moreover, if long format node
> > ID is used in the future, the code will cause little trouble for maintaining.
>
> Well, the current code doesn't support the long id (as the restriction
> of HD-audio controller side), so we'd need major changes in anyway.
> Thus this check is no big issue for maintenance, at least to me :)
Does the HDA spec define cmd format that accept long form NID?
If so, can you point me to the specific location please? Thanks.
> > what I want is to fix it during parsing connection list, and verify the node
> > id is valid there .
>
> Heh, this was already fixed :)
AFAIK, snd_hda_get_connections() won't return NIDs bigger than
0x7f(short) or 0x7ffff(long).
Thanks,
Fengguang
next prev parent reply other threads:[~2009-07-17 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 8:24 [PATCH] hda: add bounds checking for the codec command fields Wu Fengguang
2009-07-17 8:27 ` Wu Fengguang
2009-07-17 8:49 ` [PATCH] hda: add bounds checking for the codec command fields v2 Wu Fengguang
2009-07-17 9:28 ` Takashi Iwai
[not found] ` <BB1F052FCDB1EA468BD99786C8B1ED2C05871FFCB9@PDSMSX501.ccr.corp.intel.com>
[not found] ` <s5hljmn8u52.wl%tiwai@suse.de>
2009-07-17 10:53 ` Takashi Iwai
2009-07-17 11:10 ` Wu Fengguang
2009-07-17 11:05 ` Wu Fengguang [this message]
2009-07-20 2:13 ` Guo, Chaohong
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=20090717110552.GA21516@localhost \
--to=fengguang.wu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=chaohong.guo@intel.com \
--cc=jvillalo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox