:strip_exif()/u/72391/Pinky_and_the_Brain_-_Brain.gif?f=community)
Zie https://tweakers.net/nieu...eaction=7545865#r_7545865
Gelieve het artikel hierop aan te passen.
De link die ik aangeef zal morgen publiekelijk beschikbaar zijn, maar hier toch een klein cruciaal stukje:
Gelieve het artikel hierop aan te passen.
De link die ik aangeef zal morgen publiekelijk beschikbaar zijn, maar hier toch een klein cruciaal stukje:
Met andere woorden, er is nog niks van aan. Zoals ik al aangeef is er zelfs weerstand om het resterende werk te mergen wegens tal van redenen.The code merged for 4.0 is a common core that is able to support patching with both kpatch and kGraft. It provides an API that allows patch-containing modules to be inserted into the kernel; it also allows the listing and removal of patches if need be. This API performs the low-level redirection needed to replace patched functions. That is good as far as it goes, but it is missing an important component, called the "consistency model," that ensures the safety of switching between versions of a function in a running kernel. If the change is simple, it may be possible to safely make the change at any time. More complicated changes, though, may require that no kernel code is running in any of the affected functions before the switch can be done. The consistency model as found in kpatch and kGraft is where some of the biggest differences between those two implementations lie, so some work will clearly be needed to bring them together.
ASSUME makes an ASS out of U and ME
/u/12967/c5512929c5778c25c9da2378c7dbb01b.png?f=community)