From: Joe Lawrence <joe.lawrence@redhat.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Jessica Yu <jeyu@kernel.org>, Jiri Kosina <jikos@kernel.org>,
Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
Chris J Arges <chris.j.arges@canonical.com>
Subject: Re: [PATCH] livepatch: add (un)patch hooks
Date: Fri, 14 Jul 2017 09:23:29 -0400 [thread overview]
Message-ID: <20170714132329.54f763zbc7erlm5h@redhat.com> (raw)
In-Reply-To: <20170714014640.nhoowbrleu6kdka2@treble>
On Thu, Jul 13, 2017 at 08:46:40PM -0500, Josh Poimboeuf wrote:
> Date: Thu, 13 Jul 2017 20:46:40 -0500
> From: Josh Poimboeuf <jpoimboe@redhat.com>
> To: Joe Lawrence <joe.lawrence@redhat.com>
> Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org, Jessica Yu
> <jeyu@kernel.org>, Jiri Kosina <jikos@kernel.org>, Miroslav Benes
> <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>, Chris J Arges
> <chris.j.arges@canonical.com>
> Subject: Re: [PATCH] livepatch: add (un)patch hooks
> User-Agent: Mutt/1.6.0.1 (2016-04-01)
>
> On Wed, Jul 12, 2017 at 10:10:00AM -0400, Joe Lawrence wrote:
> > When the livepatch core executes klp_(un)patch_object, call out to a
> > livepatch-module specified array of callback hooks. These hooks provide
> > a notification mechanism for livepatch modules when klp_objects are
> > (un)patching. This may be most interesting when another kernel module
> > is a klp_object target and the livepatch module needs to execute code
> > after the target is loaded, but before its module_init code is run.
>
> And it's also useful for vmlinux. Patch module load/unload is separate
> from enable/disable, so the module init/exit functions can't be used for
> patch-specific changes (e.g., global data changes).
>
> > The patch-hook executes right before patching objects and the
> > unpatch-hook executes right after unpatching objects.
> >
> > Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
>
> Thanks for posting it. We found this to be a useful feature in the
> past, not quite as useful as shadow data, but still good to have for
> certain cases.
>
> Instead of "load hooks" I think it would be more accurate to call them
> "enable/disable hooks". (Maybe "callbacks" would be better than
> "hooks"? Not sure...)
Hi Josh,
I hesitataed in calling them "enable/disable" hooks as I associated
those terms at the patch level -- a livepatch might be enabled, but
callbacks for a module may not occur until its actually loaded. (I'm
fine with whatever is most intuitive to the livepatching collective :)
"Callbacks" vs. "hooks" is a good point though, as the latter has
negative connotations, especially when callers of this facility will be
mostly out of tree.
> Even better, we might want to be specific: "pre enable hooks" and "post
> disable hooks". (Or "pre patch hooks" and "post unpatch hooks"?)
> Because we might eventually decide we need the corresponding "post
> enable hooks" and "pre disable hooks" as well.
"Pre-patch" and "post-unpatch" are a bit wordy, but a good description.
I already felt it was important enough to document the order of
operations in the doc file and commit msg, so I like this idea.
> For the enable case, I think it would be a nice feature if we checked
> the return code and aborted the patching operation on error. I think
> that should be easy enough.
Yeah, that should be easy. To be specific, you're only talking about
the patching operation on the associated klp_object, not the entire
klp_patch right?
> For the unload case, it's too late to do anything, so I'd say a void
> return code would be better. Otherwise it implies that we actually do
> something about it. Maybe in that case we can leave it up to the user
> to decide whether to print an error or WARN() or whatever.
Good point. I can change that in v2.
Thanks,
-- Joe
next prev parent reply other threads:[~2017-07-14 13:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 14:09 [PATCH] livepatch hooks, revisted Joe Lawrence
2017-07-12 14:10 ` [PATCH] livepatch: add (un)patch hooks Joe Lawrence
2017-07-14 1:46 ` Josh Poimboeuf
2017-07-14 13:23 ` Joe Lawrence [this message]
2017-07-14 13:46 ` Josh Poimboeuf
2017-07-18 11:10 ` Miroslav Benes
2017-07-18 11:15 ` Miroslav Benes
2017-07-19 2:08 ` Josh Poimboeuf
2017-07-19 15:29 ` Petr Mladek
2017-07-19 19:11 ` Miroslav Benes
2017-07-17 15:51 ` Petr Mladek
2017-07-19 18:59 ` Joe Lawrence
2017-07-20 14:36 ` Petr Mladek
2017-07-19 20:49 ` Josh Poimboeuf
2017-07-20 4:17 ` Josh Poimboeuf
2017-07-20 4:20 ` Josh Poimboeuf
2017-07-20 4:30 ` Josh Poimboeuf
2017-07-20 15:50 ` Petr Mladek
2017-07-20 17:04 ` Josh Poimboeuf
2017-07-27 20:43 ` Joe Lawrence
2017-07-27 21:36 ` Josh Poimboeuf
2017-07-28 18:08 ` Joe Lawrence
2017-07-28 18:29 ` Josh Poimboeuf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170714132329.54f763zbc7erlm5h@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=chris.j.arges@canonical.com \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®