u-kernelists: where do you store per-process service info?
Posted: Sat May 09, 2015 10:02 am
Hi.
I'm trying to flesh out my u-kernel, and started to think about where to store sensitive information, such as effective user id, chroot, etc. that might get inherited by child processes. Possibilities:
Such data is stored in kernel: pros) that they can be copied to child processes on fork; can be deleted when process dies. cons) kernel has to know something about the services and how such data is inherited by child processes OR kernel fixes what data is available and processes just have to live with it.
Such data is stored in each service that needs it: pros) service related stuff is contained in the service. cons) kernel would have to let services copy their data to child processes; and let services know when processes data can be discarded.
Such data is stored in a single "container" service, and other services can store/retrieve the data they need. pros) all data in a single point, like in the kernel option, yet data outside of the kernel; easier for kernel to duplicate, discard data when needed. cons) services have to keep querying the data.
Thoughts, anyone?
I'm trying to flesh out my u-kernel, and started to think about where to store sensitive information, such as effective user id, chroot, etc. that might get inherited by child processes. Possibilities:
Such data is stored in kernel: pros) that they can be copied to child processes on fork; can be deleted when process dies. cons) kernel has to know something about the services and how such data is inherited by child processes OR kernel fixes what data is available and processes just have to live with it.
Such data is stored in each service that needs it: pros) service related stuff is contained in the service. cons) kernel would have to let services copy their data to child processes; and let services know when processes data can be discarded.
Such data is stored in a single "container" service, and other services can store/retrieve the data they need. pros) all data in a single point, like in the kernel option, yet data outside of the kernel; easier for kernel to duplicate, discard data when needed. cons) services have to keep querying the data.
Thoughts, anyone?