LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Ivan Babrou <ivan@cloudflare.com>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	kernel-team <kernel-team@cloudflare.com>
Subject: Re: Linux 4.19 and GCC 9
Date: Mon, 10 Jun 2019 16:14:17 -0300	[thread overview]
Message-ID: <20190610191417.GW21245@kernel.org> (raw)
In-Reply-To: <20190610152542.GA4132@kroah.com>

Em Mon, Jun 10, 2019 at 05:25:42PM +0200, Greg KH escreveu:
> On Mon, Jun 10, 2019 at 12:14:07PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Jun 10, 2019 at 12:21:51AM -0700, Ivan Babrou escreveu:
> > > Looks like 4.19.49 received some patches for GCC 9+, but unfortunately
> > > perf still doesn't want to compile:
> > > 
> > > [07:15:32]In file included from /usr/include/string.h:635,
> > > [07:15:32] from util/debug.h:7,
> > > [07:15:32] from builtin-help.c:15:
> > > [07:15:32]In function 'strncpy',
> > > [07:15:32] inlined from 'add_man_viewer' at builtin-help.c:192:2,
> > > [07:15:32] inlined from 'perf_help_config' at builtin-help.c:284:3:
> > > [07:15:32]/usr/include/x86_64-linux-gnu/bits/string3.h:126:10: error:
> > > '__builtin_strncpy' output truncated before terminating nul copying as
> > > many bytes from a string as its length [-Werror=stringop-truncation]
> > > [07:15:32] 126 | return __builtin___strncpy_chk (__dest, __src, __len,
> > > __bos (__dest));
> > > [07:15:32] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > [07:15:32]builtin-help.c: In function 'perf_help_config':
> > > [07:15:32]builtin-help.c:187:15: note: length computed here
> > > [07:15:32] 187 | size_t len = strlen(name);
> > > [07:15:32] | ^~~~~~~~~~~~
> > > [07:15:32]cc1: all warnings being treated as errors
> > 
> > The patch below should've taken care of that, and it has a Fixes: tag,
> > i.e. the stable scripts should've noticed that, and it was noticed with
> > gcc 8.2.
> 
> No, stable scripts do not always pick up the "Fixes:" tag, they are only

Humm, I thought it picked those, or is it that AUTOSEL thing? Ok, I'll
add stable@ when I add Fixes: then.

> guaranteed to pick up the "cc: stable@" tag.  Sometimes we catch the
> fixes ones too, but not always by far.
> 
> Anyway, I'll queue this patch up after this next round of kernels are
> released, thanks!
> 
> greg k-h

-- 

- Arnaldo

  reply	other threads:[~2019-06-10 19:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABWYdi06NUOWRLingNuybgZZsTZPjhmsOx-9oCGK94qZGYbzcw@mail.gmail.com>
     [not found] ` <CANiq72kvpiC-i53AXM-YsCUvWroHQemmqxsXjnB330ZEeHahUg@mail.gmail.com>
     [not found]   ` <CABWYdi1zhTTaN-GSgH0DnPfz7p=SRw0wts5QVYYVtfvoiS0qnQ@mail.gmail.com>
2019-05-16 21:20     ` Miguel Ojeda
2019-05-16 21:24       ` Ivan Babrou
2019-05-17  2:03       ` Josh Poimboeuf
2019-05-17  3:14         ` Ivan Babrou
2019-05-17  5:09           ` Greg KH
2019-05-17  7:38             ` Peter Zijlstra
2019-05-17  8:35               ` Miguel Ojeda
2019-05-17  8:51                 ` Greg KH
2019-05-17  9:01                   ` Miguel Ojeda
2019-05-17  9:23                     ` Greg KH
2019-05-17  9:27                       ` Miguel Ojeda
2019-05-17  9:42                         ` Greg KH
2019-05-17 11:52                           ` Greg KH
2019-05-17  9:48                     ` Greg KH
2019-05-17 15:22                     ` Arnaldo Carvalho de Melo
2019-05-17 17:23                       ` Ivan Babrou
2019-05-17 17:37                         ` Arnaldo Carvalho de Melo
2019-06-10  7:21                           ` Ivan Babrou
2019-06-10  7:45                             ` Greg KH
2019-06-10  9:32                               ` Ignat Korchagin
2019-06-10 14:21                                 ` Greg KH
2019-06-10 14:42                                   ` Miguel Ojeda
2019-06-10 14:48                                     ` Greg KH
2019-06-10 15:01                                       ` Ignat Korchagin
2019-06-10 15:04                                       ` Miguel Ojeda
2019-06-10 15:14                             ` Arnaldo Carvalho de Melo
2019-06-10 15:25                               ` Greg KH
2019-06-10 19:14                                 ` Arnaldo Carvalho de Melo [this message]
2019-06-24 10:42                                   ` Ignat Korchagin
2019-06-25  7:50                                     ` Greg KH
2019-06-25  8:08                                       ` Greg KH

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=20190610191417.GW21245@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ivan@cloudflare.com \
    --cc=jolsa@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=kernel-team@cloudflare.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --subject='Re: Linux 4.19 and GCC 9' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).