From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f50.google.com ([74.125.82.50]:37654 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754906AbcESPAo (ORCPT ); Thu, 19 May 2016 11:00:44 -0400 Received: by mail-wm0-f50.google.com with SMTP id a17so130564801wme.0 for ; Thu, 19 May 2016 08:00:38 -0700 (PDT) Subject: Fwd: Re: Inclusion for 916d4092a1d2d7b in 4.4 stable References: <573D5CF5.5050507@kyup.com> Cc: stable@vger.kernel.org To: Greg KH From: Nikolay Borisov Message-ID: <573DD50E.1090800@kyup.com> Date: Thu, 19 May 2016 18:00:30 +0300 MIME-Version: 1.0 In-Reply-To: <573D5CF5.5050507@kyup.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org List-ID: [Resending since I did mistyped the stable mailing list address] > On Wed, May 18, 2016 at 06:13:43PM +0300, Nikolay Borisov wrote: >> >> >> On 05/18/2016 06:10 PM, Greg KH wrote: >>> On Wed, May 18, 2016 at 04:02:35PM +0300, Nikolay Borisov wrote: >>>> Hello Greg, >>>> >>>> Turns out building perf is broken in the 4.4 kernel tree on centos6. >>>> Executing make in toosl/perf results in : >>>> >>>> cc1: warnings being treated as errors >>>> tests/llvm.c: In function ‘test_llvm__fetch_bpf_obj’: >>>> tests/llvm.c:53: error: declaration of ‘index’ shadows a global declaration >>>> /usr/include/string.h:489: error: shadowed declaration is here >>>> mv: cannot stat `tests/.llvm.o.tmp': No such file or directory >>>> >>>> This can be fixed by applying the following commit: >>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=916d4092a1d2d7bb50630497be71ee4c4c2807fa >>>> >>>> Would it be possible to apply it for 4.4.12 otherwise using perf from >>>> that tree is useless? >>> >>> Is this something that recently broke? Or has it always been an issue? >> >> According to the Fixes tags in the commit this broke in the following >> series: http://marc.info/?l=linux-kernel&m=144681782820358 >> >> Which was applied in November 6. 2015. So I'd say it's been fairly >> recently. > > So it's always been broken in 4.4? Or did I break it in a newer > release? Before that I was on 3.12 stable and everything worked, so I guess it did break in the release which included the aforementioned patches. > > I'll queue it up for the next round of patches, but it seems odd that no > one has reported this before, so trying to figure out why... > > thanks, > > greg k-h >