Linux 4.4.33

2016-11-18T09:49:03+00:00

Linux 4.4.32

2016-11-15T06:47:35+00:00

Linux 4.4.31

2016-11-10T15:37:00+00:00

Disable "frame-address" warning

2016-11-10T15:36:36+00:00

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

Linux 4.4.30

2016-11-01T01:56:58+00:00

Linux 4.4.29

2016-10-31T12:15:26+00:00

Linux 4.4.28

2016-10-28T07:53:25+00:00

Linux 4.4.27

2016-10-22T10:27:13+00:00

Linux 4.4.26

2016-10-20T08:01:03+00:00

Linux 4.4.25

2016-10-16T15:48:03+00:00

BMC/Intel-BMC/linux.git/Makefile, branch dev-4.4