Page MenuHomeFreeBSD

kern: document no-op handling of syscall number 0 during deregistration
ClosedPublic

Authored by go4av05.pvtx_gmail.com on Sat, Dec 20, 5:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Jan 11, 1:09 AM
Unknown Object (File)
Thu, Jan 8, 1:38 AM
Unknown Object (File)
Wed, Jan 7, 7:49 PM
Unknown Object (File)
Wed, Jan 7, 3:37 AM
Unknown Object (File)
Tue, Jan 6, 4:27 AM
Unknown Object (File)
Sat, Jan 3, 2:37 PM
Unknown Object (File)
Sat, Jan 3, 7:24 AM
Unknown Object (File)
Sat, Jan 3, 6:16 AM
Subscribers

Details

Summary

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.

Test Plan

Not applicable (comment-only change).

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

ngie added inline comments.
sys/kern/kern_syscalls.c
165–168

At first blush the comment content looks great!

Please indent all of the lines following the initial opening block to the same indentation (so, an extra space before the * on lines 166-168).

Also, I'm not sure how you contributed the patch, but it should be done following git arc create ..., etc. I would have liked to provide a suggested fix, but that isn't possible in the UI currently (I don't know if it's related to the base revision, but it might be).

go4av05.pvtx_gmail.com added a reviewer: ngie.

Enji Cooper asked to fix * alignment.
Created a patch via git diff and uploaded the patch on the phabricator website dashboard.
Did not use arc.

No Functional change intended.

sys/kern/kern_syscalls.c
165

I'm sorry if I wasn't explicit about this part in my previous comment, but this also needs to be hard-tab indented per style(9).

This revision is now accepted and ready to land.Fri, Jan 2, 7:12 AM

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.