[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150116115302.0897b895@gandalf.local.home>
Date: Fri, 16 Jan 2015 11:53:02 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Jiri Kosina <jkosina@...e.cz>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Christoph Hellwig <hch@...radead.org>,
linux-kernel@...r.kernel.org, live-patching@...r.kernel.org,
linux-next@...r.kernel.org
Subject: Re: [PATCH 1/2 v3] ftrace: don't allow IPMODIFY without proper
compiler support
On Fri, 16 Jan 2015 17:41:58 +0100 (CET)
Jiri Kosina <jkosina@...e.cz> wrote:
> On Fri, 16 Jan 2015, Steven Rostedt wrote:
>
> > Instead, make live kernel patching fail to load if fentry isn't
> > supported. IOW, instead of ftrace_ipmodify_supported, have a
> > live_kernel_patching_supported that could be based on fentry being used
> > or not.
>
> I can live with that, we are handling non-fentry case ourselves already.
>
> You expressed that you would accept such patch for ftrace in a past, so I
Right, but then I thought about it more :-)
I had a lot of time thinking about things like this while debugging
the dance between function graph and jprobes.
> thought I'll move it out from livepatching to ftrace. But if you don't
> want it now, that's not a big issue, and handling the possible fallout
> stays the responsibility of ftrace_ops "owner".
>
Exactly!
-- 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/
Powered by blists - more mailing lists