alcinnz, 23 days ago

When we're loading additional code into Linux, we'll inevitably want to remove it again! So how does Linux's delete_module syscall work?

After checking access control, copying & resolving parameters into kernelspace, logging, grabbing appropriate locks, & validating those parameters delete_module() decrements the module's refcount, calls its exit function, notifies registered callbacks, for each "livepatch" adjusts CPU datastructures whilst calling callbacks, calls debugging hook, ...

1/2?