Re: linux-next: build failure after merge of the akpm tree

From	Arnd Bergmann <arnd@arndb.de>
Newsgroups	linux.kernel
Subject	Re: linux-next: build failure after merge of the akpm tree
Date	2017-08-01 22:50 +0200
Message-ID	<u9Mh5-jv-29@gated-at.bofh.it> (permalink)
References	<u9yQN-88D-1@gated-at.bofh.it> <u9KoW-7AC-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, Aug 1, 2017 at 8:40 PM, Kees Cook <keescook@chromium.org> wrote:
>>
>> I don't know why this has turned up now.  I have just left it broken
>> for now and would appreciate any fix.
>
> Thanks for the heads-up! I'm not sure why this suddenly appeared
> either, but Arnd has sent a patch for this now.

The main difference I see that can impact gcc's optimization steps is the
unreachable() that was there in BUG() but is absent in WARN().

It's possible that the compiler decided that the entire code path leading
up to the unreachable() couldn't happen, so it dropped the
__read_overflow2() call as well.

      Arnd

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

linux-next: build failure after merge of the akpm tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-08-01 08:30 +0200
  Re: linux-next: build failure after merge of the akpm tree Kees Cook <keescook@chromium.org> - 2017-08-01 20:50 +0200
    Re: linux-next: build failure after merge of the akpm tree Arnd Bergmann <arnd@arndb.de> - 2017-08-01 22:50 +0200

csiph-web