[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181018120947.py36o462zdqjknsm@pathway.suse.cz>
Date: Thu, 18 Oct 2018 14:09:47 +0200
From: Petr Mladek <pmladek@...e.com>
To: Josh Poimboeuf <jpoimboe@...hat.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
On Wed 2018-10-17 13:35:19, Josh Poimboeuf wrote:
> I'm having trouble parsing the subject. How about:
>
> Allow unloading of patches added after using 'force'
ok
> > --- 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.
Come on! We need it just to iterate over a list of available
livepatches. The logic used to manage this list is trivial.
klp_force_transition() itself is more complicated and it
logically fits into transitions.c.
I do not want to fight over this. If you resist, I'll move it.
I just wanted to share my view.
Best Regards,
Petr
Powered by blists - more mailing lists