Steven Rostedt (Red Hat) (1): ring-buffer: Remove duplicate use of '&' in recursive code ---- kernel/trace/ring_buffer.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) --------------------------- commit 7eb867195b9f3990da60738b1f26d0a71f37f77f Author: Steven Rostedt (Red Hat) <rostedt@xxxxxxxxxxx> Date: Fri Mar 27 17:39:49 2015 -0400 ring-buffer: Remove duplicate use of '&' in recursive code A clean up of the recursive protection code changed val = this_cpu_read(current_context); val--; val &= this_cpu_read(current_context); to val = this_cpu_read(current_context); val &= val & (val - 1); Which has a duplicate use of '&' as the above is the same as val = val & (val - 1); Actually, it would be best to remove that line altogether and just add it to where it is used. Link: http://lkml.kernel.org/alpine.DEB.2.11.1503271423580.23114@xxxxxxxxxx Suggested-by: Christoph Lameter <cl@xxxxxxxxx> Signed-off-by: Steven Rostedt <rostedt@xxxxxxxxxxx> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c index 922048a0f7ea..93caf56567cb 100644 --- a/kernel/trace/ring_buffer.c +++ b/kernel/trace/ring_buffer.c @@ -2705,8 +2705,7 @@ static __always_inline void trace_recursive_unlock(void) { unsigned int val = __this_cpu_read(current_context); - val &= val & (val - 1); - __this_cpu_write(current_context, val); + __this_cpu_write(current_context, val & (val - 1)); } #else -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html