>>> On 20.06.17 at 17:59, wrote:
> Our mechanism when deploying livepatches is to replace the loaded
> livepatch with another one. Which means we only have on livepatch
> applied and during the upgrade process have to load another one.
I think this is the main problematic part here: You're trying
On Tue, Jun 20, 2017 at 01:51:41AM -0600, Jan Beulich wrote:
> >>> On 20.06.17 at 04:47, wrote:
> > This way we can load livepatches with symbol names that
> > are the same as long as they are local ('static').
> >
> > The use case here is to replace an existing livepatch
> > with a newer one - a
>>> On 20.06.17 at 04:47, wrote:
> This way we can load livepatches with symbol names that
> are the same as long as they are local ('static').
>
> The use case here is to replace an existing livepatch
> with a newer one - and one which has the same local symbols.
>
> Without this patch we get:
