linux-kernel - Re: [PATCH 1/2] ring-buffer: fix deadlock from reader_lock in read

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20081112102518.GC24482@elte.hu>
Date:	Wed, 12 Nov 2008 11:25:18 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Steven Rostedt <srostedt@...hat.com>
Subject: Re: [PATCH 1/2] ring-buffer: fix deadlock from reader_lock in
	read_start


* Steven Rostedt <rostedt@...dmis.org> 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@...hat.com>
> ---
>  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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/