Lines Matching full:patch

59 a live patch is called with the help of a custom ftrace handler. But there are
77 But there are more complex fixes. For example, a patch might change
78 ordering of locking in multiple functions at the same time. Or a patch
97 switch over.  When a patch is enabled, livepatch enters into a
100 sequence occurs when a patch is disabled, except the tasks converge from
108 safe to patch tasks:
112    the task is patched.  In most cases this will patch most or all of
141 Unless we can come up with another way to patch kthreads, architectures
145 The /sys/kernel/livepatch/<patch>/transition file shows whether a patch
146 is in transition.  Only a single patch can be in transition at a given
147 time.  A patch can remain in transition indefinitely, if any of the tasks
148 are stuck in the initial patch state.
151 opposite value to the /sys/kernel/livepatch/<patch>/enabled file while
153 converge back to the original patch state.
157 If a patch is in transition, this file shows 0 to indicate the task is
158 unpatched and 1 to indicate it's patched.  Otherwise, if no patch is in
168 /sys/kernel/livepatch/<patch>/force attribute. Writing 1 there clears
173 tasks) and request a clearance from a patch distributor to force the transition.
175 patch, which functions are (un)patched, and which functions the blocking tasks
176 are sleeping in (/proc/<pid>/stack may help here). Removal (rmmod) of patch
179 reference count if a patch module is disabled and enabled in a loop.
199    location to switch the kthread's patch state would be at a designated
216    b) patching kthreads and idle tasks at their designated patch points.
219    user tasks and waking kthreads to patch them.  But it could still be
248 The patch contains only functions that are really modified. But they
258 The patch is described by several structures that split the information
284     the patch itself and the relevant functions might be patched
292     synchronously. The whole patch is applied only when all patched
296     For more details on how the patch is applied on a per-task basis,
307 exclusive. They have the same result for the given patch but
314 The only reasonable way is to enable the patch when the livepatch kernel
321 the patch cannot get enabled.
334 /sys/kernel/livepatch/<name>. The patch is rejected when any above
363 All enabled patches might get replaced by a cumulative patch that
366 Once the new patch is enabled and the 'transition' finishes then
370 freed when the related function is not modified by the new patch
384 the previously enabled patch or even the original one. This stage is
391 patch are removed from the corresponding struct klp_ops. The ftrace handler
404 to a new patch state (patched/unpatched) without being forced it is
415 /sys/kernel/livepatch/<patch>/force attributes allow administrator to affect a
454     the return address. The first user wins. Either the probe or the patch