linux-kernel - Re: [PATCHv3] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH

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: <20170209131452.472aa882@gandalf.local.home>
Date:   Thu, 9 Feb 2017 13:14:52 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Russell King - ARM Linux <linux@...linux.org.uk>
Cc:     Abel Vesa <abelvesa@...ux.com>, mingo@...hat.com,
        viro@...iv.linux.org.uk, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org, jjhiblot@...phandler.com,
        pmladek@...e.com, robin.murphy@....com, zhouchengming1@...wei.com,
        Masami Hiramatsu <mhiramat@...nel.org>
Subject: Re: [PATCHv3] arm: ftrace: Adds support for
 CONFIG_DYNAMIC_FTRACE_WITH_REGS


[ sending again with Masami Cc'd ]

On Thu, 9 Feb 2017 13:14:14 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Thu, 9 Feb 2017 18:06:44 +0000
> Russell King - ARM Linux <linux@...linux.org.uk> wrote:
> 
> > On Thu, Feb 09, 2017 at 12:13:22PM -0500, Steven Rostedt wrote:  
> > > Then came along live kernel patching, which I believe this series is
> > > trying to support. What is needed by pt_regs is a way to "hijack" the
> > > function being called to instead call the patched function. That is,
> > > ftrace is not being used for tracing, but in reality, being used to
> > > modify the running kernel. It is being used to change what function
> > > gets called. ftrace is just a hook for that mechanism.    
> > 
> > So, would I be correct to assume that the only parts of pt_regs that
> > would be touched are those which contain arguments to the function,
> > and the register which would contain the return value?
> >   
> 
> For live kernel patching, perhaps.
> 
> But for kprobes, I think they can touch anything. Matters what the
> creater of the kprobe wanted to do.
> 
> -- Steve