Linux Kernel Oops on module unload

[hmwildermuth]

A kernel oops is often caused on module unload. This is because a process can start a faulted blocking syscall, such as wait4 or select, then have the syscall table flushed and the module unloaded, so that when the syscall continues execution it is in the memory where the kernel module once was, causing a page fault.

[woodruffw]

Hmm, it's not a mitigation, but we could special-case these calls in krfctl and warn the user that enabling them is known to cause this.