linux-kernel - Re: [PATCH] ring_buffer: enlarge RB_MAX_SMALL

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]

Date:	Wed, 15 Apr 2009 10:23:40 -0400
From:	Steven Rostedt <srostedt@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Lai Jiangshan <laijs@...fujitsu.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ring_buffer: enlarge RB_MAX_SMALL_DATA


On Wed, 2009-04-15 at 16:12 +0200, Ingo Molnar wrote:
> * Steven Rostedt <srostedt@...hat.com> wrote:

> Yeah - format specifications are always good. They weaken ABI 
> bindings and allow more flexibility both on the tool and the kernel 
> side.
> 
> > We could ask Linus to pull this into 30 because it is a API 
> > change.
> 
> Apps could assume if the format file is not there it's the .30 
> format.

My fear is that they are written before the change, and will not know
about a format file existing. Then those apps will break on 31.

But this is still new, and the only user I know of at the moment is the
University student doing the ftrace GUI. I'll keep him informed.

Thanks,

-- Steve


--
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/