Lines Matching +full:pre +full:- +full:its

5 Livepatch (un)patch-callbacks provide a mechanism for livepatch modules
10   - Safe updates to global data
12   - "Patches" to init and probe functions
14   - Patching otherwise unpatchable code (i.e. assembly)
25   - Module init/exit code doesn't run when disabling and re-enabling a
28   - A module notifier can't stop a to-be-patched module from loading.
39   * Pre-patch
40                  - before a klp_object is patched
42   * Post-patch
43                  - after a klp_object has been patched and is active
46   * Pre-unpatch
47                  - before a klp_object is unpatched (ie, patched code is
48                    active), used to clean up post-patch callback
51   * Post-unpatch
52                  - after a klp_object has been patched, all code has
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
68 A callback is only executed if its host klp_object is loaded.  For
69 in-kernel vmlinux targets, this means that callbacks will always execute
72 module target is (un)loaded, its callbacks will execute only if the
75 The pre-patch callback, if specified, is expected to return a status
76 code (0 for success, -ERRNO on error).  An error status code indicates
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:
82   - Refuse to load a livepatch, if the livepatch is loaded after
87   - Refuse to load a module, if the livepatch was already successfully
90 No post-patch, pre-unpatch, or post-unpatch callbacks will be executed
94 If a patch transition is reversed, no pre-unpatch handlers will be run
95 (this follows the previously mentioned symmetry -- pre-unpatch callbacks
96 will only occur if their corresponding post-patch callback executed).
100 only the post-unpatch callback will be called.
110 ------------------
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,
123 -----------------------------------------
125 Although __init and probe functions are not directly livepatch-able, it
126 may be possible to implement similar updates via pre/post-patch
129 The commit ``48900cb6af42 ("virtio-net: drop NETIF_F_FRAGLIST")`` change the way that
130 virtnet_probe() initialized its driver's net_device features.  A
131 pre/post-patch callback could iterate over all such devices, making a