Commit Graph

419 Commits

Author SHA1 Message Date
cgd 3cec79bb72 add counters for vmstat 1993-05-07 07:12:43 +00:00
cgd db3da84702 add bruce evans's useracc fixes, from patchkit patch 137. 1993-05-07 07:03:50 +00:00
cgd b235aec4f6 fix free page count determination 1993-05-07 06:59:45 +00:00
cgd fd7c50fd61 patch from Pete Chown <pc123@cus.cam.ac.uk> to fix mmap
modes vs. read/write permissions problem.
1993-05-07 01:58:11 +00:00
cgd 645b67012b make it panic, like i thought it did, for mb_map too small. 1993-04-29 08:57:02 +00:00
mycroft 0b48d59355 Fix utter inanity I committed last night. 1993-04-29 00:46:21 +00:00
mycroft a203e5704b Implement previous change more cleanly. 1993-04-28 04:00:49 +00:00
mycroft 87dc98f60b Introduce a new panic() condition in case I missed something. 1993-04-28 03:04:57 +00:00
mycroft 95090f0a13 Don't use first block of swap area. 1993-04-28 03:04:25 +00:00
mycroft 235bd1db44 Add consistent multiple-inclusion protection. 1993-04-19 03:45:34 +00:00
glass 33d009a09c Prevents you from creating double faults and such mmaping stuff on top
of the kernel, etc. Tested.  Derived from BSDI public patches
1993-04-10 15:06:01 +00:00
cgd 4493ba8058 fixed stupid typo (missing comma) in hand-applied diff 1993-04-09 17:19:02 +00:00
cgd a128c34f9c From: Guido van Rooij <guido@gvr.win.tue.nl>
when mmapping a file, permissions are checked as it should be. When
mprotect()-ing the address range afterwards, no protection was checked
regarding the protection of the file originally opened. So
when you open /usr/bin/su RDONLY and SHARED you could afterwards change
the mmapped region to READ|WRITE. This gave the possibility to obtain
root privs obviously.
1993-04-09 17:16:30 +00:00
cgd 202313150e changes, running on sef's machine to good effect, likely contributed
by torek.  (sef told me to get them, and their origin...)
1993-04-09 17:13:17 +00:00
cgd 827c75471f From: andrew@werple.apana.org.au (Andrew Herbert)
Here are some fixes I derived from the mach 3.0 VM system a couple of months
ago.  At the time, I was giving the memory object routines a good looking
at, trying to fix the long-standing problem where vm_object_collapse()
sometimes fails to collapse objects left over from the exit of a forked
child.  As bde has noted, the problem seems to occur when portions of the
parent are paged out.  These "lost" memory objects, which can eat up a huge
amount of swap space, are reclaimed when the parent responsible for the
fork()s is killed.
1993-04-09 16:53:46 +00:00
cgd 3cac22992d from sean eric fagan:
it seems to keep the vm system from deadlocking the system when it runs
out of swap + physical memory.
prevents the system from giving the last page(s) to anything but the
referenced "processes" (especially important is the pager process,
which should never have to wait for a free page).
1993-04-09 15:54:56 +00:00
cgd 64354bb7c6 broke out panics for *_map too small, and tried to coalesce the maps more
often.
1993-03-31 21:53:56 +00:00
cgd e541169ce2 after 0.2.2 "stable" patches applied 1993-03-21 18:04:42 +00:00
cgd 61f282557f initial import of 386bsd-0.1 sources 1993-03-21 09:45:37 +00:00