Lines Matching refs:post
39 active), used to clean up post-patch callback
48 symmetry: pre-patch callbacks have a post-unpatch counterpart and
49 post-patch callbacks have a pre-unpatch counterpart. An unpatch
77 No post-patch, pre-unpatch, or post-unpatch callbacks will be executed
83 will only occur if their corresponding post-patch callback executed).
87 only the post-unpatch callback will be called.
102 patch the data *after* patching is complete with a post-patch callback,
111 may be possible to implement similar updates via pre/post-patch
116 pre/post-patch callback could iterate over all such devices, making a
125 pre/post-(un)patch combination, but a selection that demonstrates a few
152 to the klp_patch, their post-patch callbacks run and the transition
167 unpatching transition starts. klp_objects are reverted, post-patch
199 On livepatch enable, only pre/post-patch callbacks are executed for
211 When a targeted module is subsequently loaded, only its pre/post-patch
221 livepatch_callbacks_mod) pre/post-unpatch callbacks are executed:
269 post-unpatch callbacks are executed when this occurs:
277 When the livepatch is disabled, pre and post-unpatch callbacks are run
316 pre/post-patch callbacks are executed:
326 post-unpatch callbacks are executed when this occurs:
366 As expected, only pre/post-(un)patch handlers are executed for vmlinux:
445 module. Notice that no post-patch or pre/post-unpatch callbacks are
455 However, pre/post-unpatch callbacks run for the vmlinux klp_object:
492 notice that the post-patch callbacks are executed and the transition
574 module). Note that *no* post-patch callbacks will be executed while the
591 klp_object's post-patch callbacks executed, the remaining klp_object's