public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "arnd@arndb.de" <arnd@arndb.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"keescook@chromium.org" <keescook@chromium.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"parav@mellanox.com" <parav@mellanox.com>,
	"monis@mellanox.com" <monis@mellanox.com>,
	"Michal.Kalderon@cavium.com" <Michal.Kalderon@cavium.com>,
	"sean.hefty@intel.com" <sean.hefty@intel.com>,
	"danielmicay@gmail.com" <danielmicay@gmail.com>,
	"Ariel.Elior@cavium.com" <Ariel.Elior@cavium.com>,
	"hal.rosenstock@gmail.com" <hal.rosenstock@gmail.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"dledford@redhat.com" <dledford@redhat.com>,
	"noaos@mellanox.com" <noaos@mellanox.com>
Subject: Re: [PATCH] infiniband: avoid overflow warning
Date: Mon, 31 Jul 2017 16:17:35 +0000	[thread overview]
Message-ID: <1501517853.2466.12.camel@wdc.com> (raw)
In-Reply-To: <CAK8P3a1r22C-Uxs93OSbS4_eRNhKUTv8xwc6wwGahE80whCjyA@mail.gmail.com>

On Mon, 2017-07-31 at 18:04 +0200, Arnd Bergmann wrote:
> On Mon, Jul 31, 2017 at 5:32 PM, Bart Van Assche <Bart.VanAssche@wdc.com> wrote:
> > So inetaddr_event() assigns AF_INET so .sin_family and gcc warns about code
> > that is only executed if .sin_family == AF_INET6? Since this warning is the
> > result of incorrect interprocedural analysis by gcc, shouldn't this be
> > reported as a bug to the gcc authors?
> 
> I think the interprocedural analysis here is just a little worse than it could
> be, but it's not actually correct.  It's not gcc that prints the warning (if
> it did, then I'd agree it would be a gcc bug) but the warning is triggered
> intentionally by the fortified version of memcpy in include/linux/string.h.
> 
> The problem as I understand it is that gcc cannot guarantee that it
> tracks the value of addr->sa_family at  least as far as the size of the
> stack object, and it has no strict reason to do so, so the inlined
> rdma_ip2gid() will still contain both cases.

Hello Arnd,

Had you already considered to uninline the rdma_ip2gid() function?

Bart.

  reply	other threads:[~2017-07-31 16:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31  6:50 [PATCH] infiniband: avoid overflow warning Arnd Bergmann
2017-07-31  7:08 ` Moni Shoua
2017-07-31  7:30   ` Arnd Bergmann
2017-07-31 15:32     ` Bart Van Assche
2017-07-31 16:04       ` Arnd Bergmann
2017-07-31 16:17         ` Bart Van Assche [this message]
2017-07-31 19:19           ` Arnd Bergmann
2017-07-31 19:35             ` Daniel Micay
2017-07-31 20:58     ` Kees Cook
2017-07-31 21:10       ` Arnd Bergmann
2017-07-31 21:18         ` Kees Cook
2017-07-31 21:37           ` Daniel Micay
2017-07-31 21:52           ` Arnd Bergmann
2017-07-31 22:06             ` Kees Cook
2017-08-18 16:40 ` Doug Ledford

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=1501517853.2466.12.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=Ariel.Elior@cavium.com \
    --cc=Michal.Kalderon@cavium.com \
    --cc=arnd@arndb.de \
    --cc=danielmicay@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=monis@mellanox.com \
    --cc=noaos@mellanox.com \
    --cc=parav@mellanox.com \
    --cc=sean.hefty@intel.com \
    /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