Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1666373

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

From Stephen Rothwell <sfr@canb.auug.org.au>
Newsgroups linux.kernel
Subject Re: linux-next: build failure after merge of the akpm-current tree
Date 2017-06-15 04:10 +0200
Message-ID <tSsoq-4ML-7@gated-at.bofh.it> (permalink)
References <tOUjg-8cR-17@gated-at.bofh.it> <tSrVn-4m9-5@gated-at.bofh.it> <tSseJ-4tL-1@gated-at.bofh.it> <tSseJ-4tL-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

Hi Daniel,

On Wed, 14 Jun 2017 21:58:42 -0400 Daniel Micay <danielmicay@gmail.com> wrote:
>
> They're false positive warnings. I think objtool has a list of
> __noreturn functions and needs fortify_panic added there. It's just a
> warning so it doesn't need to happen immediately.

There are *lots* of them, so it does need to be fixed (Linus will be
very irritated if it hits his tree like that).  Create a patch to
objtool and get the x86 guys to Ack it?

-- 
Cheers,
Stephen Rothwell

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

Thread

Re: linux-next: build failure after merge of the akpm-current tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-15 03:40 +0200
  Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-15 04:00 +0200
    Re: linux-next: build failure after merge of the akpm-current tree Daniel Micay <danielmicay@gmail.com> - 2017-06-15 04:00 +0200
      Re: linux-next: build failure after merge of the akpm-current tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-15 04:10 +0200
        Re: linux-next: build failure after merge of the akpm-current tree Daniel Micay <danielmicay@gmail.com> - 2017-06-15 04:20 +0200
          Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-15 04:30 +0200
            Re: linux-next: build failure after merge of the akpm-current tree Daniel Micay <danielmicay@gmail.com> - 2017-06-15 04:40 +0200
    Re: linux-next: build failure after merge of the akpm-current tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-15 04:10 +0200
      Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-15 04:20 +0200
        Re: linux-next: build failure after merge of the akpm-current tree Daniel Micay <danielmicay@gmail.com> - 2017-06-15 05:20 +0200
          Re: linux-next: build failure after merge of the akpm-current tree Michael Ellerman <mpe@ellerman.id.au> - 2017-06-15 08:00 +0200
            Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-15 17:20 +0200
    Re: linux-next: build failure after merge of the akpm-current tree Andrew Morton <akpm@linux-foundation.org> - 2017-06-15 21:20 +0200
      Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-16 01:50 +0200
        Re: linux-next: build failure after merge of the akpm-current tree Daniel Micay <danielmicay@gmail.com> - 2017-06-16 02:10 +0200
          Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-16 02:40 +0200
            Re: linux-next: build failure after merge of the akpm-current tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-16 03:30 +0200
        Re: linux-next: build failure after merge of the akpm-current tree Andrew Morton <akpm@linux-foundation.org> - 2017-06-16 19:20 +0200
          Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-19 22:30 +0200

csiph-web