[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2d92bc17-0844-54dd-b6ea-8d89ce2d590b@redhat.com>
Date: Wed, 22 Jan 2020 10:15:11 +0000
From: Julien Thierry <jthierry@...hat.com>
To: Petr Mladek <pmladek@...e.com>, Jiri Kosina <jikos@...nel.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Miroslav Benes <mbenes@...e.cz>
Cc: Joe Lawrence <joe.lawrence@...hat.com>,
Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
Nicolai Stange <nstange@...e.de>,
live-patching@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [POC 11/23] livepatch: Safely detect forced transition when
removing split livepatch modules
Hi Petr,
On 1/17/20 3:03 PM, Petr Mladek wrote:
> The information about forced livepatch transition is currently stored
> in struct klp_patch. But there is not any obvious safe way how to
> access it when the split livepatch modules are removed.
>
If that's the only motivation to do this, klp_objects could have a
reference to the klp_patch they are part of. This could easily be set
when adding the klp_object to the klp_patch->obj_list in
klp_init_object_early() .
Having this reference could also prove useful in future scenarios.
Cheers,
--
Julien Thierry
Powered by blists - more mailing lists