src/sys/miscfs/procfs/procfs_map.c, branch release/3.0.0_cvs

This commit was manufactured by cvs2svn to create tag

1999-01-21T00:55:32+00:00

'RELENG_3_0_0_RELEASE'.

This commit was manufactured to restore the state of the 3.0-RELEASE image.
Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

This commit was manufactured by cvs2svn to create tag

1999-01-21T00:55:32+00:00

'RELENG_3_0_0_RELEASE'.

Examine all occurrences of sprintf(), strcat(), and str[n]cpy()

1998-12-04T22:54:57+00:00

for possible buffer overflow problems. Replaced most sprintf()'s
with snprintf(); for others cases, added terminating NUL bytes where
appropriate, replaced constants like "16" with sizeof(), etc.

These changes include several bug fixes, but most changes are for
maintainability's sake. Any instance where it wasn't "immediately
obvious" that a buffer overflow could not occur was made safer.

Reviewed by:	Bruce Evans 
Reviewed by:	Matthew Dillon 
Reviewed by:	Mike Spengler

Tighten up management of memory and swap space during map allocation,

1998-04-29T04:28:22+00:00

deallocation cycles.  This should provide a measurable improvement
on swap and memory allocation on loaded systems.  It is unlikely a
complete solution.  Also, provide more map info with procfs.
Chuck Cranor spurred on this improvement.

Back out DIAGNOSTIC changes.

1998-02-06T12:14:30+00:00

Turn DIAGNOSTIC into a new-style option.

1998-02-04T22:34:03+00:00

Make our v_usecount vnode reference count work identically to the

1998-01-06T05:26:17+00:00

original BSD code.  The association between the vnode and the vm_object
no longer includes reference counts.  The major difference is that
vm_object's are no longer freed gratuitiously from the vnode, and so
once an object is created for the vnode, it will last as long as the
vnode does.

When a vnode object reference count is incremented, then the underlying
vnode reference count is incremented also.  The two "objects" are now
more intimately related, and so the interactions are now much less
complex.

When vnodes are now normally placed onto the free queue with an object still
attached.  The rundown of the object happens at vnode rundown time, and
happens with exactly the same filesystem semantics of the original VFS
code.  There is absolutely no need for vnode_pager_uncache and other
travesties like that anymore.

A side-effect of these changes is that SMP locking should be much simpler,
the I/O copyin/copyout optimizations work, NFS should be more ponderable,
and further work on layered filesystems should be less frustrating, because
of the totally coherent management of the vnode objects and vnodes.

Please be careful with your system while running this code, but I would
greatly appreciate feedback as soon a reasonably possible.

Don't try to obtain an excluive lock on the vm map, since a deadlock might

1997-11-14T22:57:46+00:00

occur if the process owning the map is wiring pages.

Removed unused #includes.

1997-08-02T14:33:27+00:00

Don't include in the kernel. Stage 1: don't include

1997-03-24T11:25:10+00:00

it when it is not used.  In most cases, the reasons for including it
went away when the special ioctl headers became self-sufficient.