Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751658AbdGaU6h (ORCPT ); Mon, 31 Jul 2017 16:58:37 -0400 Received: from mail-io0-f170.google.com ([209.85.223.170]:37892 "EHLO mail-io0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751046AbdGaU6g (ORCPT ); Mon, 31 Jul 2017 16:58:36 -0400 MIME-Version: 1.0 In-Reply-To: References: <20170731065016.2947796-1-arnd@arndb.de> From: Kees Cook Date: Mon, 31 Jul 2017 13:58:34 -0700 X-Google-Sender-Auth: 8haPm5vWlsV9UToH5OJQeA_9fh8 Message-ID: Subject: Re: [PATCH] infiniband: avoid overflow warning To: Arnd Bergmann Cc: Moni Shoua , Doug Ledford , Sean Hefty , Hal Rosenstock , Daniel Micay , "Kalderon, Michal" , Ariel Elior , "David S. Miller" , Bart Van Assche , Parav Pandit , Noa Osherovich , linux-rdma , Linux Kernel Mailinglist Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1228 Lines: 32 On Mon, Jul 31, 2017 at 12:30 AM, Arnd Bergmann wrote: > On Mon, Jul 31, 2017 at 9:08 AM, Moni Shoua wrote: >> On Mon, Jul 31, 2017 at 9:50 AM, Arnd Bergmann wrote: >>> --- a/include/rdma/ib_addr.h >>> +++ b/include/rdma/ib_addr.h >>> @@ -172,7 +172,8 @@ static inline int rdma_ip2gid(struct sockaddr *addr, union ib_gid *gid) >>> (struct in6_addr *)gid); >>> break; >>> case AF_INET6: >>> - memcpy(gid->raw, &((struct sockaddr_in6 *)addr)->sin6_addr, 16); >>> + *(struct in6_addr *)&gid->raw = >>> + ((struct sockaddr_in6 *)addr)->sin6_addr; This seems reasonable. >>> break; >>> default: >>> return -EINVAL; >> what happens if you replace 16 with sizeof(struct in6_addr)? > > Same thing: the problem is that gcc already knows the size of the structure we > pass in here, and it is in fact shorter. So gcc is ignoring both the cast (to 16 byte struct in6_addr) and the caller's actual 128 byte struct sockaddr_storage, and looking only at struct sockaddr? That seems really weird. -Kees -- Kees Cook Pixel Security