From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH for-xen-4.5] stubdom: another for fix for lwip compile
Date: Tue, 7 Oct 2014 18:18:23 +0200 [thread overview]
Message-ID: <20141007161823.GC2983@type> (raw)
In-Reply-To: <1412691346-20511-1-git-send-email-olaf@aepfle.de>
Olaf Hering, le Tue 07 Oct 2014 16:15:46 +0200, a écrit :
> stubdom/lwip-x86_64/src/core/dhcp.c: In function 'dhcp_create_request':
> stubdom/lwip-x86_64/src/core/dhcp.c:1361:64: error: array subscript is above array bounds
>
> The previous attempt to fix the failure above worked fine in SLE11,
> openSUSE 13.1 and newer. But gcc-4.5 as included in openSUSE 11.4 still
> failed to compile. To fix compilation also with this version of gcc move
> the range check right into the code instead of assigning it to a
> temporary variable.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
> Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
> Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Acked-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
> ---
> stubdom/lwip.dhcp_create_request-hwaddr_len.patch | 15 +--------------
> 1 file changed, 1 insertion(+), 14 deletions(-)
>
> diff --git a/stubdom/lwip.dhcp_create_request-hwaddr_len.patch b/stubdom/lwip.dhcp_create_request-hwaddr_len.patch
> index 12f1014..c43f282 100644
> --- a/stubdom/lwip.dhcp_create_request-hwaddr_len.patch
> +++ b/stubdom/lwip.dhcp_create_request-hwaddr_len.patch
> @@ -1,26 +1,13 @@
> ----
> - lwip-x86_64/src/core/dhcp.c | 4 +++-
> - 1 file changed, 3 insertions(+), 1 deletion(-)
> -
> Index: src/core/dhcp.c
> ===================================================================
> --- src/core/dhcp.c
> +++ src/core/dhcp.c
> -@@ -1322,6 +1322,8 @@ dhcp_create_request(struct netif *netif)
> - {
> - struct dhcp *dhcp;
> - u16_t i;
> -+ /* gcc can not know if hwaddr_len exceeds the hwaddr array size */
> -+ u8_t hwaddr_len = netif->hwaddr_len > NETIF_MAX_HWADDR_LEN ? NETIF_MAX_HWADDR_LEN : netif->hwaddr_len;
> - LWIP_ERROR("dhcp_create_request: netif != NULL", (netif != NULL), return ERR_ARG;);
> - dhcp = netif->dhcp;
> - LWIP_ERROR("dhcp_create_request: dhcp != NULL", (dhcp != NULL), return ERR_VAL;);
> @@ -1356,7 +1358,7 @@ dhcp_create_request(struct netif *netif)
> dhcp->msg_out->giaddr.addr = 0;
> for (i = 0; i < DHCP_CHADDR_LEN; i++) {
> /* copy netif hardware address, pad with zeroes */
> - dhcp->msg_out->chaddr[i] = (i < netif->hwaddr_len) ? netif->hwaddr[i] : 0/* pad byte*/;
> -+ dhcp->msg_out->chaddr[i] = (i < hwaddr_len) ? netif->hwaddr[i] : 0/* pad byte*/;
> ++ dhcp->msg_out->chaddr[i] = (i < (netif->hwaddr_len > NETIF_MAX_HWADDR_LEN ? NETIF_MAX_HWADDR_LEN : netif->hwaddr_len)) ? netif->hwaddr[i] : 0/* pad byte*/;
> }
> for (i = 0; i < DHCP_SNAME_LEN; i++) {
> dhcp->msg_out->sname[i] = 0;
>
--
Samuel
Running Windows on a Pentium is like having a brand new Porsche but only
be able to drive backwards with the handbrake on.
(Unknown source)
next prev parent reply other threads:[~2014-10-07 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 14:15 [PATCH for-xen-4.5] stubdom: another for fix for lwip compile Olaf Hering
2014-10-07 16:18 ` Samuel Thibault [this message]
2014-10-08 12:56 ` Ian Campbell
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=20141007161823.GC2983@type \
--to=samuel.thibault@ens-lyon.org \
--cc=olaf@aepfle.de \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.