linux-kernel - Re: [PATCH 0/7] [GIT PULL][for 2.6.31] ring-buffer: various clean ups

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: <20090620152635.GA6748@elte.hu>
Date:	Sat, 20 Jun 2009 17:26:35 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 0/7] [GIT PULL][for 2.6.31] ring-buffer: various clean
	ups


* Steven Rostedt <rostedt@...dmis.org> wrote:

> Ingo,
> 
> Please pull the latest tip/tracing/urgent tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/urgent
> 
> 
> Steven Rostedt (7):
>       ring-buffer: use BUF_PAGE_HDR_SIZE in calculating index
>       ring-buffer: remove useless warn on check
>       ring-buffer: remove useless compile check for buffer_page size
>       ring-buffer: check for less than two in size allocation
>       ring-buffer: add locks around rb_per_cpu_empty
>       ring-buffer: do not grab locks in nmi
>       ring-buffer: have benchmark test print to trace buffer
> 
> ----
>  kernel/trace/ring_buffer.c           |   82 ++++++++++++++++++++++++---------
>  kernel/trace/ring_buffer_benchmark.c |   37 ++++++++-------
>  2 files changed, 78 insertions(+), 41 deletions(-)

Pulled, thanks a lot 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/