linux-kernel - Re: [PATCH 00/19] [GIT PULL][v3.6] ftrace: Allow kprobes to work with ftace

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120731151242.GA20169@gmail.com>
Date:	Tue, 31 Jul 2012 17:12:42 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH 00/19] [GIT PULL][v3.6] ftrace: Allow kprobes to work
 with ftace


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

> On Fri, 2012-07-20 at 22:19 -0400, Steven Rostedt wrote:
> > Ingo,
> > 
> > This patch series extends ftrace function tracing utility to be
> > more dynamic for its users. It allows for data passing to the callback
> > functions, as well as reading regs as if a breakpoint were to trigger
> > at function entry.
> > 
> > The main goal of this patch series was to allow kprobes to use ftrace
> > as an optimized probe point when a probe is placed on an ftrace nop.
> > With lots of help from Masami Hiramatsu, and going through lots of
> > iterations, we finally came up with a good solution.
> > 
> > I've tested it vigorously (although, like always, there may be some
> > subtle bug), but I feel it is ready for inclussion for the 3.6 merge
> > window.
> 
> As the merge window opened the day after I sent this (which 
> was also the same day I left for vacation :-p ), I recommend 
> that this goes in v3.7.

Yeah, the timing was a bit unfortunate :-/

> Can you pull this in for 3.7, or do you want me to post 
> another pull request after the merge window closes?

No need to resend, will pull it once the merge window dust has 
settled a bit.

Thanks,

	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/