kernel/vfs: Consistently check if MALLOC_DECLARE was defined.

Keep these checks even in _KERNEL context and even if <sys/malloc.h>
is included before. Helps a lot for userland testing.

kernel: Make chflags syscalls argument types consistent with userland.

There was an inconsistency between userland and syscalls argument types
that was inherited after initial fork. Adjust protot

kernel: Make chflags syscalls argument types consistent with userland.

There was an inconsistency between userland and syscalls argument types
that was inherited after initial fork. Adjust prototypes to use u_long
and add missing const char* too. Rerun sysent. Change tmpfs/dirfs to
use u_int for flags since mask for superuser changeable flags is
SF_SETTABLE 0xffff0000 (most fs use uint32_t), adjust mksubr script.
Remove no longer needed (u_long) casts I could find elsewhere.

While there, adjust unistd.h prototypes to use generic types too.

show more ...

dirfs - Add kqueue(2) support

- Based on tmpfs work on 80ae59d743
- FIFO ops not added

dirfs - Change debug levels

- Specific debug levels are specified for easier debugging:

1 Calls to VFS operations (mount, umount, ...)
3 Calls to VN operations (open, close, rea

dirfs - Change debug levels

- Specific debug levels are specified for easier debugging:

1 Calls to VFS operations (mount, umount, ...)
3 Calls to VN operations (open, close, read, ...)
5 Calls to subroutines
9 Everything

- Once dirfs is stabilised, debugging facilities will go and
only KTR will remain.

show more ...

dirfs - only expose inlines to the kernel

* Only expose inlines to kernel code, user code can get tripped up on
things like KKASSERT().

dirfs - Rework how host file permissions are checked.

* Retrieve uid/gid of the user running the vkernel on mount time
instead of on every open(2).

Bring in DIRFS: A filesystem for VKERNELS

* What is DIRFS?
dirfs is a pseudo-filesystem specific for vkernel(7) which allows mounting
host's directories into the vkernel. It runs directly in the

Bring in DIRFS: A filesystem for VKERNELS

* What is DIRFS?
dirfs is a pseudo-filesystem specific for vkernel(7) which allows mounting
host's directories into the vkernel. It runs directly in the vkernel's VFS
code, as any other regular filesystem, but it does syscalls (vkernels are
userland programs) to retrieve or post the information needed on every
operation requested.

Needless to say that the operations that you can perform in the host
directories/files depend on the permissions the user that runs the vkernel.
For example, you will not be able to 'chflags schg' if you run the vkernel
with a regular user and not with root.

* How does it work?
It basically works like any other filesystem. It has its own mount_dirfs
command that will be called by the system's mount(8) command when needed.

vkernel64 # mount -t dirfs /usr/src2 /mnt
vkernel64 # df -h /mnt
Filesystem Size Used Avail Capacity Mounted on
dirfs@/usr/src2 47G 36G 12G 75% /mnt

Umounting is a normal operation too:

vkernel64 # mount | fgrep dirfs
dirfs@/usr/src2 on /mnt (dirfs)
vkernel64 # umount /mnt

* What's the current status
Currently it is in a *experimental* status, with (probably) many bugs and some
parts missing.

TODO
- Make dirfs mpsafe.
- Fix problems with multiple mount points.
- Implement VOP_NLINK so that hardlinks are possible.
- Add missing kqueue(2) support.
- dirfs root so that a vkernel can be booted from it.
- Locking mechanisms for opened fds between host <-> vkernel.
- Make sure dirfs is properly restored after vkernel checkpointing
(upcoming GSoC project).
- Bug hunting & bug fixing.
- Any ideas?

show more ...