[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.21.1710181504360.8638@san.suse.cz>
Date: Wed, 18 Oct 2017 15:05:51 +0200 (CEST)
From: Miroslav Benes <mbenes@...e.cz>
To: Joe Lawrence <joe.lawrence@...hat.com>
cc: live-patching@...r.kernel.org, linux-kernel@...r.kernel.org,
Josh Poimboeuf <jpoimboe@...hat.com>,
Jessica Yu <jeyu@...nel.org>, Jiri Kosina <jikos@...nel.org>,
Petr Mladek <pmladek@...e.com>,
Chris J Arges <chris.j.arges@...onical.com>
Subject: Re: [PATCH v6 1/3] livepatch: add (un)patch callbacks
On Fri, 13 Oct 2017, Joe Lawrence wrote:
> Provide livepatch modules a klp_object (un)patching notification
> mechanism. Pre and post-(un)patch callbacks allow livepatch modules to
> setup or synchronize changes that would be difficult to support in only
> patched-or-unpatched code contexts.
>
> Callbacks can be registered for target module or vmlinux klp_objects,
> but each implementation is klp_object specific.
>
> - Pre-(un)patch callbacks run before any (un)patching transition
> starts.
>
> - Post-(un)patch callbacks run once an object has been (un)patched and
> the klp_patch fully transitioned to its target state.
>
> Example use cases include modification of global data and registration
> of newly available services/handlers.
>
> See Documentation/livepatch/callbacks.txt for details and
> samples/livepatch/ for examples.
>
> Signed-off-by: Joe Lawrence <joe.lawrence@...hat.com>
Acked-by: Miroslav Benes <mbenes@...e.cz>
Miroslav
Powered by blists - more mailing lists