Page MenuHomeFreeBSD

makesyscalls: permit a range of syscall numbers for UNIMPL
ClosedPublic

Authored by emaste on Jan 29 2018, 7:09 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Nov 1, 7:07 PM
Unknown Object (File)
Sat, Nov 1, 7:07 PM
Unknown Object (File)
Sat, Nov 1, 7:07 PM
Unknown Object (File)
Sat, Nov 1, 7:07 PM
Unknown Object (File)
Sat, Nov 1, 2:53 PM
Unknown Object (File)
Mon, Oct 20, 8:06 PM
Unknown Object (File)
Sep 30 2025, 11:06 PM
Unknown Object (File)
Sep 23 2025, 5:04 AM
Subscribers

Details

Summary

Some ABIs have large gaps in syscall numbers. Allow gaps to be filled as ranges of UNIMPL, with an entry like:

248-1023        AUE_NULL        UNIMPL  dummy

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

In general I like the approach. It's easy enough to extend to other keywords in the future if needed as well.

sys/kern/makesyscalls.sh
630

I guess it isn't obvious to me that syscall_range[2] would always be valid. Does awk return '0' for out-of-range array access? Hmm, seems like it returns the empty string probably from the manpage. I wonder if it would be cleaner to explicitly set syscall_range[2] to syscall in the 'n ==1' case and then this loop could just be 'while (syscall <= syscall_range[2])'?

This revision is now accepted and ready to land.Jan 30 2018, 1:20 AM

Always set syscall_range[2] as suggested by jhb

This revision now requires review to proceed.Jan 30 2018, 2:00 AM
This revision is now accepted and ready to land.Jan 30 2018, 6:16 PM
This revision was automatically updated to reflect the committed changes.