Clarify why kern_syscall_deregister() treats syscall number 0 as a no-op.
Syscall number 0 is reserved and is not dynamically registered, so
returning success simplifies module unload paths.
No functional change intended.
Differential D54326
kern: document no-op handling of syscall number 0 during deregistration Authored by go4av05.pvtx_gmail.com on Sat, Dec 20, 5:48 PM. Tags None Referenced Files
Details Clarify why kern_syscall_deregister() treats syscall number 0 as a no-op. Syscall number 0 is reserved and is not dynamically registered, so No functional change intended. Not applicable (comment-only change).
Diff Detail
Event Timeline
Comment Actions Enji Cooper asked to fix * alignment. No Functional change intended. Comment Actions I'll take up the patch and fix up the whitespace bug since it's a trivial change which adds helpful documentation. In general, please submit patches in the future that follow style(9) so they can be accepted more frictionlessly. | ||||||||||||||||||||||||||||||||||