linux-kernel - Re: [for-next][PATCH 0/4] ftrace: Add dynamic trampoline support

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]

Date:	Thu, 30 Oct 2014 18:08:01 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Steven Rostedt <rostedt@...dmis.org>
cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Josh Poimboeuf <jpoimboe@...hat.com>,
	Vojtech Pavlik <vojtech@...e.cz>,
	Seth Jennings <sjenning@...hat.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [for-next][PATCH 0/4] ftrace: Add dynamic trampoline support

On Thu, 30 Oct 2014, Steven Rostedt wrote:

> > > This adds the allocation of dynamic trampolines. It still does not
> > > allow for dynamic ftrace_ops to use them on CONFIG_PREEMPT systems.
> > > That will come in 3.20, as I want to test out call_rcu_tasks() for
> > > a bit first on my own boxes.
> > > 
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> > > for-next
> > > 
> > > Head SHA1: 9fd7caf67913fbf35d834beaa8f9764d733a9236
> > > 
> > > 
> > > Steven Rostedt (Red Hat) (4):
> > >       ftrace/x86: Add dynamic allocated trampoline for ftrace_ops
> > >       ftrace/x86: Show trampoline call function in enabled_functions
> > >       ftrace/x86: Allow !CONFIG_PREEMPT dynamic ops to use allocated trampolines
> > >       ftrace: Add more information to ftrace_bug() output
> > 
> > FWIW I just did a very quick test, and kGraft seems to run flawlessly on 
> > top of this.
> > 
> 
> Does that mean I can add your Tested-by: for all these patches?

Yup, Tested-by: is fine by me, thanks.

I haven't yet read the code though, so anything other than this tag isn't 
applicable.

-- 
Jiri Kosina
SUSE Labs
--
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/