[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181017183519.wfc2n54ga6cyjhfi@treble>
Date: Wed, 17 Oct 2018 13:35:19 -0500
From: Josh Poimboeuf <jpoimboe@...hat.com>
To: Petr Mladek <pmladek@...e.com>
Cc: Jiri Kosina <jikos@...nel.org>, Miroslav Benes <mbenes@...e.cz>,
Jason Baron <jbaron@...mai.com>,
Joe Lawrence <joe.lawrence@...hat.com>,
Evgenii Shatokhin <eshatokhin@...tuozzo.com>,
live-patching@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v13 05/12] livepatch: Refuse to unload only livepatches
available during a forced transition
I'm having trouble parsing the subject. How about:
Allow unloading of patches added after using 'force'
?
> --- a/kernel/livepatch/core.c
> +++ b/kernel/livepatch/core.c
> @@ -45,7 +45,8 @@
> */
> DEFINE_MUTEX(klp_mutex);
>
> -static LIST_HEAD(klp_patches);
> +/* Registered patches */
> +LIST_HEAD(klp_patches);
Instead of making this non-static, can we just move
klp_force_transition() to core.c? It's nice to have all the list
management code encapsulated in the same file.
--
Josh
Powered by blists - more mailing lists