From: Takashi Iwai <tiwai@suse.de>
To: Joe Perches <joe@perches.com>
Cc: alsa-devel@alsa-project.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: hda - Fix and neaten print_nid_path/debug_badness
Date: Mon, 07 Jul 2014 09:35:07 +0200 [thread overview]
Message-ID: <s5hegxxei50.wl%tiwai@suse.de> (raw)
In-Reply-To: <1404590522.6384.62.camel@joe-AO725>
At Sat, 05 Jul 2014 13:02:02 -0700,
Joe Perches wrote:
>
> print_nid_path has a possible buffer overflow if
> struct nid_path.path values are > 256.
>
> Avoid this and neaten the output to remove the leading ':'
>
> Neaten debug_badness to always verify arguments.
>
> Signed-off-by: Joe Perches <joe@perches.com>
Thanks, applied.
Although the overflow would never happen in practice (the id can't be
over 8 bit from the definition in the HD-audio controller side), it's
still better to have a proper check.
Takashi
> ---
> sound/pci/hda/hda_generic.c | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/sound/pci/hda/hda_generic.c b/sound/pci/hda/hda_generic.c
> index 589e47c..b293583 100644
> --- a/sound/pci/hda/hda_generic.c
> +++ b/sound/pci/hda/hda_generic.c
> @@ -350,16 +350,16 @@ static void print_nid_path(struct hda_codec *codec,
> const char *pfx, struct nid_path *path)
> {
> char buf[40];
> + char *pos = buf;
> int i;
>
> + *pos = 0;
> + for (i = 0; i < path->depth; i++)
> + pos += scnprintf(pos, sizeof(buf) - (pos - buf), "%s%02x",
> + pos != buf ? ":" : "",
> + path->path[i]);
>
> - buf[0] = 0;
> - for (i = 0; i < path->depth; i++) {
> - char tmp[4];
> - sprintf(tmp, ":%02x", path->path[i]);
> - strlcat(buf, tmp, sizeof(buf));
> - }
> - codec_dbg(codec, "%s path: depth=%d %s\n", pfx, path->depth, buf);
> + codec_dbg(codec, "%s path: depth=%d '%s'\n", pfx, path->depth, buf);
> }
>
> /* called recursively */
> @@ -1700,9 +1700,11 @@ static int fill_and_eval_dacs(struct hda_codec *codec,
> #define DEBUG_BADNESS
>
> #ifdef DEBUG_BADNESS
> -#define debug_badness(fmt, args...) codec_dbg(codec, fmt, ##args)
> +#define debug_badness(fmt, ...) \
> + codec_dbg(codec, fmt, ##__VA_ARGS__)
> #else
> -#define debug_badness(...)
> +#define debug_badness(fmt, ...) \
> + do { if (0) codec_dbg(codec, fmt, ##__VA_ARGS__); } while (0)
> #endif
>
> #ifdef DEBUG_BADNESS
>
>
prev parent reply other threads:[~2014-07-07 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 20:02 Joe Perches
2014-07-07 7:35 ` 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=s5hegxxei50.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®