Lines Matching refs:patch
5 Livepatch (un)patch-callbacks provide a mechanism for livepatch modules
16 In most cases, (un)patch callbacks will need to be used in conjunction
26 patch.
39 * Pre-patch
42 * Post-patch
48 active), used to clean up post-patch callback
54 used to cleanup pre-patch callback resources
61 symmetry: pre-patch callbacks have a post-unpatch counterpart and
62 post-patch callbacks have a pre-unpatch counterpart. An unpatch
63 callback will only be executed if its corresponding patch callback was
64 executed. Typical use cases pair a patch handler that acquires and
70 when a livepatch is enabled/disabled. For patch target kernel modules,
75 The pre-patch callback, if specified, is expected to return a status
78 safe and to stop the current patching request. (When no pre-patch
80 pre-patch callback returns failure, the kernel's module loader will:
90 No post-patch, pre-unpatch, or post-unpatch callbacks will be executed
91 for a given klp_object if the object failed to patch, due to a failed
94 If a patch transition is reversed, no pre-unpatch handlers will be run
96 will only occur if their corresponding post-patch callback executed).
98 If the object did successfully patch, but the patch transition never
99 started for some reason (e.g., if another object failed to patch),
112 A pre-patch callback can be useful to update a global variable. For
118 patch the data *after* patching is complete with a post-patch callback,
126 may be possible to implement similar updates via pre/post-patch
131 pre/post-patch callback could iterate over all such devices, making a