Re:OpenBSD System-Call Pinning
by IAmLiterallyAB on Saturday February 03, 2024 @12:38AM
(#39237821)
Even those get most of their info from /proc and /sys rather than special syscalls
On the BSDs they sure don't, /proc (for its role referred to) and /sys are peculiar to Linux, /proc is not even mounted by default on FreeBSD, is deprecated and doesn't exist on OpenBSD. On OpenBSD/FreeBSD most of the info comes out with sysctl(3) or reading kernel memory directly.
> reading kernel memory directly
God I hope not
https://man.freebsd.org/cgi/man.cgi?query=kvm&sektion=3&n=1
The aforementioned tools use these interfaces.
Most of the sundry information for the live kernel comes from sysctl (abstracted by kvm), I note the mem/kmem interface for completeness.
I do not know what the previous poster was talking about, but, while unrestricted access to kernel memory is of course unacceptable, a perfectly secure and useful means for the kernel to provide information to a user process is to map a page as read-only in the user address space, from where the user process could get the information without the overhead of a system call.
For information of general interest such a special kernel page could be mapped as read-only in the address space of all user processes.
Much of the information that is provided in the special file systems /proc and /sys could have been provided in some appropriate data structures in such read-only shared memory, for a faster access, by avoiding the overhead of file system calls and of file text parsing.
Yes, if you're writing netstat or lsof or ps or something, you need tight coupling with the binary and the kernel, and you can argue Linux does that better, but most people aren't writing netstat or lsof or ps.