Re: [PATCH 1/2] ring-buffer: fix deadlock from reader_lock inread_start

[Ingo Molnar]

* Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

> Impact: deadlock fix in ring_buffer_read_start
> 
> The ring_buffer_iter_reset was called from ring_buffer_read_start
> where both grabbed the reader_lock.
> 
> This patch separates out the internals of ring_buffer_iter_reset
> to its own function so that both APIs may grab the reader_lock.
> 
> Signed-off-by: Steven Rostedt <srostedt@xxxxxxxxxx>
> ---
>  kernel/trace/ring_buffer.c |   29 +++++++++++++++++------------
>  1 files changed, 17 insertions(+), 12 deletions(-)

applied to tip/tracing/ring-buffer, thanks Steve!

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/