| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
this can cause other problems.
|
|
|
|
|
|
|
| |
via getnewvnode();
ok art@,tedu@
tested by todd@
|
|
|
|
|
|
|
|
| |
actually allocate "desiredvnodes" - add a vdrop to un-hold a vnode held
with vhold, and change the name cache to make use of vhold/vdrop, while
keeping track of which vnodes are referred to by which cache entries to
correctly hold/drop vnodes when the cache uses them.
ok thib@, tedu@, art@
|
|
|
|
|
|
|
|
| |
many assumptions were made about the way the various list types are
implemented.
lots of suggestions and help from otto and miod.
ok otto@
|
| |
|
|
|
|
| |
to compile in our tree.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- cache_lookup
move common code from various fs's here
always return with vnode and parent locked
adjust return codes
- PDIRUNLOCK - new flag set if lookup couldn't lock parent vnode
- kernfs and procfs
lock vnode in get_root
don't unlock (again) in kernfs_freevp
fix memory leak in procfs
From tedu@stanford.edu
deraadt@ and various other ok
|
| |
|
|
|
|
| |
Too many new features and fixes to mention here.
|
| |
|
|
|