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: <alpine.DEB.2.00.0907231005470.20997@gandalf.stny.rr.com>
Date:	Thu, 23 Jul 2009 10:06:30 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 0/2] [GIT PULL] tracing: various fixes


On Wed, 22 Jul 2009, Steven Rostedt wrote:

> 
> Ingo,
> 
> These two patches are built against my last push, but perhaps these
> should go to 2.6.31. The first one fixes a bug that makes the 
> printk_format file useless (making trace_bprintk useless for binary
> readers). The other is a bug with the way the files may be truncated
> incorrectly.

I may pull these over to urgent. They probably should go into 31.

I'll make another pull request there instead.

Thanks,

-- Steve

> 
> Please pull the latest tip/tracing/core-1 tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/core-1
> 
> 
> Steven Rostedt (2):
>       tracing: show proper address for trace-printk format
>       tracing: only truncate ftrace files when O_TRUNC is set
> 
> ----
>  kernel/trace/ftrace.c       |    4 ++--
>  kernel/trace/trace.c        |    2 +-
>  kernel/trace/trace_events.c |    2 +-
>  kernel/trace/trace_printk.c |    2 +-
>  4 files changed, 5 insertions(+), 5 deletions(-)
> -- 
> 
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ