Initial take on mountpoints

Mountpoints arent always associated with file_object, for example /proc/sys/fs (o.sys.sysctl.fs.t) is a mountpoint for binfmt_misc filesystems but is not considered a file object (it is a pseudo filesystem "file" object instead)
It is safe to say that mountpoints are objects, and this is why access to mointpoints is managed in the object module and not the file module

Subjects associated with object_unconfined_subject can mounton directory types associated with object_mountpoint_object
Always associate object types used to mount filesystems on with object_mountpoint_object. I would add a neverallow rule that prevents mounton anything but object_mountpoint_object but currently that seems not worth the complexity

Fedora hard-codes security contexts on early boot. Causing mount trying to mount on directories with invalid contexts)

When the system is done booting things are labeled properly, so i suppose the contexts do get reset.

debugfs on /sys/kernel/debug
Make sure / is labeled properly
o.fs.rootfs.t is a mountpoint (obviously)
Initial partitioning of top level files

Tmpfs is mounted under /run
Create a type attribute, blockabstract and macro for tmpfs files
/run/user is just another run file
Create equivalence /run /var/run (because it is still required unless you want to modify a dozen systemd units, and tmpfilesd config files
add some tests, useless i know but i had to test so might as well automate it