kern: document no-op handling of syscall number 0 during deregistration
Needs ReviewPublic
Actions

Authored by go4av05.pvtx_gmail.com on Sat, Dec 20, 5:48 PM.

Tags

None

Referenced Files

	F140265411: D54326.id168473.diff
	Mon, Dec 22, 1:20 AM

	F140238805: D54326.id168473.diff
	Sun, Dec 21, 6:28 PM

	Unknown Object (File)
	Sun, Dec 21, 7:32 AM

	Unknown Object (File)
	Sun, Dec 21, 5:12 AM

Subscribers

imp

olce

This revision needs review, but there are no reviewers specified.

Details

Reviewers: None

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

go4av05.pvtx_gmail.com created this revision.Sat, Dec 20, 5:48 PM

Herald added subscribers: olce, imp. · View Herald TranscriptSat, Dec 20, 5:48 PM

go4av05.pvtx_gmail.com requested review of this revision.Sat, Dec 20, 5:48 PM

Revision Contents
Changeset List

Path

Size

sys/

kern/

kern_syscalls.c

9 lines

Diff 168473

View Options

kern: document no-op handling of syscall number 0 during deregistrationNeeds ReviewPublicActions