mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miroslav Benes <mbenes@suse.cz>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Joe Lawrence <joe.lawrence@redhat.com>,
	live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jessica Yu <jeyu@kernel.org>, Jiri Kosina <jikos@kernel.org>,
	Petr Mladek <pmladek@suse.com>,
	Chris J Arges <chris.j.arges@canonical.com>
Subject: Re: [PATCH] livepatch: add (un)patch hooks
Date: Tue, 18 Jul 2017 13:10:50 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.20.1707181306200.24826@pobox.suse.cz> (raw)
In-Reply-To: <20170714134650.6jzb5utzfq6muvxo@treble>


> > > 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?
> 
> Oh, right, I forgot about modules.  We can't stop the module from
> loading, so forget that.  Maybe the load hook should just return void.

We can. We can stop a patch module from being loaded if there is an error 
coming from a hook, or we can stop a patched module (patch module is 
loaded) from being loaded. The latter case is not very user-friendly. We 
have force_load_module sysfs attribute for exactly these cases (if an 
admin is sure he can safely do that). It is not nice though.
 
> > > 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.

I agree with this point.

Miroslav

  reply	other threads:[~2017-07-18 11:10 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
2017-07-14 13:46       ` Josh Poimboeuf
2017-07-18 11:10         ` Miroslav Benes [this message]
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=alpine.LSU.2.20.1707181306200.24826@pobox.suse.cz \
    --to=mbenes@suse.cz \
    --cc=chris.j.arges@canonical.com \
    --cc=jeyu@kernel.org \
    --cc=jikos@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --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®