[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170106210444.o35ajlxnfow27p33@treble>
Date: Fri, 6 Jan 2017 15:04:44 -0600
From: Josh Poimboeuf <jpoimboe@...hat.com>
To: Miroslav Benes <mbenes@...e.cz>
Cc: Jessica Yu <jeyu@...hat.com>, Jiri Kosina <jikos@...nel.org>,
Petr Mladek <pmladek@...e.com>, linux-kernel@...r.kernel.org,
live-patching@...r.kernel.org,
Michael Ellerman <mpe@...erman.id.au>,
Heiko Carstens <heiko.carstens@...ibm.com>, x86@...nel.org,
linuxppc-dev@...ts.ozlabs.org, linux-s390@...r.kernel.org,
Vojtech Pavlik <vojtech@...e.com>, Jiri Slaby <jslaby@...e.cz>,
Chris J Arges <chris.j.arges@...onical.com>,
Andy Lutomirski <luto@...nel.org>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v3 13/15] livepatch: change to a per-task consistency
model
On Thu, Jan 05, 2017 at 10:34:57AM +0100, Miroslav Benes wrote:
>
> > @@ -740,6 +809,14 @@ int klp_register_patch(struct klp_patch *patch)
> > return -ENODEV;
> >
> > /*
> > + * Architectures without reliable stack traces have to set
> > + * patch->immediate because there's currently no way to patch kthreads
> > + * with the consistency model.
> > + */
> > + if (!klp_have_reliable_stack() && !patch->immediate)
> > + return -ENOSYS;
> > +
>
> I think an error message (pr_err) would be appropriate here.
>
> $ insmod patch_1.ko
> insmod: ERROR: could not insert module patch_1.ko: Function not implemented
>
> is not helpful much :)
Ok :-)
--
Josh
Powered by blists - more mailing lists