pooka 3557ef52b9 In case the operations thread has exited, do not queue any more ... operations. This prevents kernel memory leaks (one of which happened every time the file system was unmounted via PUFFSOP_UNMOUNT ... and incidentally would've been trivially caught with the old malloc(9) interface. I wonder if the message is to use a ton of pools instead of regression-attractive kmem interface).		2010-01-14 19:50:07 +00:00
..
files.puffs	Part 2/n of extensive changes to request transport to/from userspace:	2007-11-10 21:45:04 +00:00
Makefile
puffs_msgif.c	In case the operations thread has exited, do not queue any more	2010-01-14 19:50:07 +00:00
puffs_msgif.h	Add a PUFFS_UNMOUNT server->kernel request, which causes the kernel	2010-01-07 22:45:31 +00:00
puffs_node.c	Kill suspend support. It was never implemented correctly:	2009-11-05 19:42:44 +00:00
puffs_subr.c	more <sys/buf.h> police	2008-11-16 19:34:29 +00:00
puffs_sys.h	Rename PUFFS_SOPREQ_EXIT to PUFFS_SOPREQSYS_EXIT to better signal	2010-01-07 23:02:34 +00:00
puffs_vfsops.c	In case the operations thread has exited, do not queue any more	2010-01-14 19:50:07 +00:00
puffs_vnops.c	Since VOP_GETATTR() does not require a locked vnode, resolve and	2010-01-14 14:44:13 +00:00
TODO	add some todo-items, based on a file which was lingering in my	2009-05-18 15:47:28 +00:00