qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Stefan Weil <sw@weilnetz.de>
Cc: Andrzej Zaborowski <andrew.zaborowski@intel.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/wm8750: Fix potential buffer overflow
Date: Mon, 10 Sep 2012 15:17:30 +0200	[thread overview]
Message-ID: <20120910131730.GT6791@ohm.aurel32.net> (raw)
In-Reply-To: <1346705760-11648-1-git-send-email-sw@weilnetz.de>

On Mon, Sep 03, 2012 at 10:56:00PM +0200, Stefan Weil wrote:
> Report from smatch:
> 
> hw/wm8750.c:369 wm8750_tx(12) error: buffer overflow 's->i2c_data' 2 <= 2
> 
> It looks like the preprocessor statements were simply misplaced.
> 
> Replace also __FUNCTION__ by __func__ to please checkpatch.pl.
> 
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
>  hw/wm8750.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/wm8750.c b/hw/wm8750.c
> index 11bcec3..44f138f 100644
> --- a/hw/wm8750.c
> +++ b/hw/wm8750.c
> @@ -361,10 +361,10 @@ static int wm8750_tx(I2CSlave *i2c, uint8_t data)
>      uint16_t value;
>  
>      if (s->i2c_len >= 2) {
> -        printf("%s: long message (%i bytes)\n", __FUNCTION__, s->i2c_len);
>  #ifdef VERBOSE
> -        return 1;
> +        printf("%s: long message (%i bytes)\n", __func__, s->i2c_len);
>  #endif
> +        return 1;
>      }
>      s->i2c_data[s->i2c_len ++] = data;
>      if (s->i2c_len != 2)
> -- 
> 1.7.10
> 

Thanks, applied.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

      parent reply	other threads:[~2012-09-10 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-03 20:56 [Qemu-devel] [PATCH] hw/wm8750: Fix potential buffer overflow Stefan Weil
2012-09-03 22:14 ` Peter Maydell
2012-09-10 13:17 ` Aurelien Jarno [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=20120910131730.GT6791@ohm.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=andrew.zaborowski@intel.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.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;
as well as URLs for NNTP newsgroup(s).