[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180428050026.GA29422@kroah.com>
Date: Sat, 28 Apr 2018 07:00:26 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Teck Choon Giam <giamteckchoon@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, acme@...nel.org,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>
Subject: Re: kernel-4.9.94 compile error: 'KMOD_DECOMP_LEN' undeclared
On Fri, Apr 27, 2018 at 10:28:27AM -0700, Randy Dunlap wrote:
> [adding some Cc:]
>
> On 04/14/2018 02:41 AM, Teck Choon Giam wrote:
> > Hi,
> >
> > Compile linux-4.9.94 will have error related to KMOD_DECOMP_LEN
> > undeclared. Searching string related to KMOD_DECOMP_LEN in
> > linux-4.9.94 and linux-4.15.17 sources as below:
> >
> > <mock-chroot>sh-4.2# grep -r KMOD_DECOMP_LEN ./linux-4.15.17
> > ./linux-4.15.17/tools/perf/tests/code-reading.c: char
> > decomp_name[KMOD_DECOMP_LEN];
> > ./linux-4.15.17/tools/perf/util/dso.h:#define KMOD_DECOMP_LEN
> > sizeof(KMOD_DECOMP_NAME)
> > ./linux-4.15.17/tools/perf/util/annotate.c: char tmp[KMOD_DECOMP_LEN];
> > ./linux-4.15.17/tools/perf/util/dso.c: char newpath[KMOD_DECOMP_LEN];
> > sh-4.2# grep -r KMOD_DECOMP_LEN ./linux-4.9.94
> > ./linux-4.9.94/tools/perf/tests/code-reading.c: char
> > decomp_name[KMOD_DECOMP_LEN];
> > ./linux-4.9.94/tools/perf/util/dso.c: char newpath[KMOD_DECOMP_LEN];
> >
> > So I guess for linux-4.9.94 has not define KMOD_DECOMP_LEN in
> > tools/perf/util/dso.h?
>
>
> 4.9.9[456] lack:
> #define KMOD_DECOMP_NAME "/tmp/perf-kmod-XXXXXX"
> #define KMOD_DECOMP_LEN sizeof(KMOD_DECOMP_NAME)
>
>
> However, the commit that added those macros does not apply cleanly to 4.9.96.
>
> commit 42b3fa670825983fc8bd0ac7b80cc84ae3abb75b
> Author: Namhyung Kim <namhyung@...nel.org>
> Date: Thu Jun 8 16:31:03 2017 +0900
>
> perf tools: Introduce dso__decompress_kmodule_{fd,path}
This should now be fixed in the latest 4.9.y -rc release, right?
If not, please let me know as I though I resolved this problem there...
thanks,
greg k-h
Powered by blists - more mailing lists