qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Thomas Monjalon <thomas_ml@monjalon.net>
Cc: Thomas Monjalon <thomas@monjalon.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] e1000: fix build on Ubuntu with _FORTIFY_SOURCE
Date: Thu, 8 Apr 2010 21:32:46 +0200	[thread overview]
Message-ID: <20100408193246.GJ6056@volta.aurel32.net> (raw)
In-Reply-To: <1270027371-25548-1-git-send-email-thomas_ml@monjalon.net>

On Wed, Mar 31, 2010 at 11:22:51AM +0200, Thomas Monjalon wrote:
> From: Thomas Monjalon <thomas@monjalon.net>
> 
> There was a pointer cast warning on Ubuntu since _FORTIFY_SOURCE has been reenabled.
> 
> _FORTIFY_SOURCE had been disabled by 4a24470497360d8b77568b83008d0e9d6eb0787d
> and reenabled by 849583050d5f6f782718be8cb50688978973fbea.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>

Thanks, applied.

> ---
>  hw/e1000.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/hw/e1000.c b/hw/e1000.c
> index fd3059a..34cc451 100644
> --- a/hw/e1000.c
> +++ b/hw/e1000.c
> @@ -642,7 +642,7 @@ e1000_receive(VLANClientState *nc, const uint8_t *buf, size_t size)
>  
>      if (vlan_enabled(s) && is_vlan_packet(s, buf)) {
>          vlan_special = cpu_to_le16(be16_to_cpup((uint16_t *)(buf + 14)));
> -        memmove((void *)(buf + 4), buf, 12);
> +        memmove((uint8_t *)buf + 4, buf, 12);
>          vlan_status = E1000_RXD_STAT_VP;
>          vlan_offset = 4;
>          size -= 4;
> -- 
> 1.7.0.3
> 
> 
> 
> 
> 
> 

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

      reply	other threads:[~2010-04-08 21:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  9:22 [Qemu-devel] [PATCH] e1000: fix build on Ubuntu with _FORTIFY_SOURCE Thomas Monjalon
2010-04-08 19:32 ` 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=20100408193246.GJ6056@volta.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.org \
    --cc=thomas@monjalon.net \
    --cc=thomas_ml@monjalon.net \
    /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).