Linux 3.16.50

2017-11-11T13:34:06Z

Disable "frame-address" warning

2017-11-11T13:33:41Z

commit 124a3d88fa20e1869fc229d7d8c740cc81944264 upstream. Newer versions of gcc warn about the use of __builtin_return_address() with a non-zero argument when "-Wall" is specified: kernel/trace/trace_irqsoff.c: In function ‘stop_critical_timings’: kernel/trace/trace_irqsoff.c:433:86: warning: calling ‘__builtin_return_address’ with a nonzero argument is unsafe [-Wframe-address] stop_critical_timing(CALLER_ADDR0, CALLER_ADDR1); [ .. repeats a few times for other similar cases .. ] It is true that a non-zero argument is somewhat dangerous, and we do not actually have very many uses of that in the kernel - but the ftrace code does use it, and as Stephen Rostedt says: "We are well aware of the danger of using __builtin_return_address() of > 0. In fact that's part of the reason for having the "thunk" code in x86 (See arch/x86/entry/thunk_{64,32}.S). [..] it adds extra frames when tracking irqs off sections, to prevent __builtin_return_address() from accessing bad areas. In fact the thunk_32.S states: 'Trampoline to trace irqs off. (otherwise CALLER_ADDR1 might crash)'." For now, __builtin_return_address() with a non-zero argument is the best we can do, and the warning is not helpful and can end up making people miss other warnings for real problems. So disable the frame-address warning on compilers that need it. Acked-by: Steven Rostedt Signed-off-by: Linus Torvalds Signed-off-by: Greg Kroah-Hartman Signed-off-by: Arnd Bergmann Signed-off-by: Ben Hutchings

Linux 3.16.49

2017-10-12T14:28:25Z

Linux 3.16.48

2017-09-15T17:30:20Z

Linux 3.16.47

2017-08-26T01:14:52Z

Linux 3.16.46

2017-07-18T17:40:42Z

Linux 3.16.45

2017-07-02T16:13:04Z

Linux 3.16.44

2017-06-05T20:17:26Z

Linux 3.16.43

2017-04-04T21:21:58Z

Linux 3.16.42

2017-03-16T02:27:28Z

user/sven/linux.git/Makefile, branch v3.16.50