On Mon 2019-02-11 11:05:16, Joe Lawrence wrote: > Add a simple livepatch versioning policy to the livepatch core. For > those klp_patches with non-zero version, only load those with higher > versions than the livepatch core's latest-version. Livepatches may opt > out of the policy altogether (i.e. patches always load and do not update > latest-version) by specifying klp_patch.version=0. I think that a more practical would be a per-feature/per-callback-set versions. We currently support many code streams. By definition, there are more released livepatches for older kernels that for recent ones. It might be error prone to decide about a particular feature by a global version that would be different in different code streams. Best Regards, Petr PS: I would like to start working on the support soon. Of course, it depends how many things come into my way.
