On Fri, Mar 19, 2021 at 02:21:46PM -0700, Guenter Roeck wrote:
On Fri, Mar 19, 2021 at 01:18:19PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.182 release. There are 8 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sun, 21 Mar 2021 12:17:37 +0000. Anything received after that time might be too late.
Build results: total: 155 pass: 154 fail: 1 Failed builds: x86_64:tools/perf Qemu test results: total: 420 pass: 420 fail: 0
jvmti/jvmti_agent.c:48:21: error: static declaration of ‘gettid’ follows non-static declaration 48 | static inline pid_t gettid(void) | ^~~~~~ In file included from /usr/include/unistd.h:1170, from jvmti/jvmti_agent.c:33: /usr/include/x86_64-linux-gnu/bits/unistd_ext.h:34:16: note: previous declaration of ‘gettid’ was here
The tools/perf error is not new. It is seen because I started updating my servers to Ubuntu 20.0. The following patches would be needed to fix the problem in v4.19.y.
8feb8efef97a tools build feature: Check if get_current_dir_name() is available 11c6cbe706f2 tools build feature: Check if eventfd() is available 4541a8bb13a8 tools build: Check if gettid() is available before providing helper fc8c0a992233 perf tools: Use %define api.pure full instead of %pure-parser
The first two patches prevent a conflict with the third patch, and the last patch fixes an unrelated build warning.
Older kernels are also affected. The list of patches needed for v4.14.y is:
0ada120c883d perf: Make perf able to build with latest libbfd (this patch is in v4.9.y but not in v4.14.y) 25ab5abf5b14 tools build feature: Check if pthread_barrier_t is available 8feb8efef97a tools build feature: Check if get_current_dir_name() is available 11c6cbe706f2 tools build feature: Check if eventfd() is available 4541a8bb13a8 tools build: Check if gettid() is available before providing helper fc8c0a992233 perf tools: Use %define api.pure full instead of %pure-parser
I tried to fix the problem in v4.9.y and v4.4.y as well, but that is pretty much hopeless. I'll have to stop testing perf builds for those kernels.
I'll suck these in for the next round of releases, thanks.
and thanks for testing.
greg k-h