src/sys/kern/kern_malloc.c, branch release/4.6.2_cvsFreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=release%2F4.6.2_cvs2002-08-14T06:57:09ZThis commit was manufactured by cvs2svn to create tag2002-08-14T06:57:09Zcvs2svncvs2svn@FreeBSD.org2002-08-14T06:57:09Zurn:sha1:72b7f92e6edf4375820f765b41697b3208ce7fe7
'RELENG_4_6_2_RELEASE'.
This commit was manufactured to restore the state of the 4.6.2-RELEASE image.
Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.
MFC: (rev. 1.94) Add realloc() and reallocf() and allow free(NULL).2002-03-16T02:19:51ZArchie Cobbsarchie@FreeBSD.org2002-03-16T02:19:51Zurn:sha1:7a775bca15018d1e45c95855cfdd53c4fbd309e8MFC: the TUNABLE_*() API update, but I have left a backwards compatability2001-07-26T18:53:03ZPeter Wemmpeter@FreeBSD.org2001-07-26T18:53:03Zurn:sha1:4984c7e2d2b86b2d20e4b48f8bb52e899e36e3fb
emulation of TUNABLE_INT_DECL() for older drivers. TUNABLE_INT_FETCH()
is not backwards compatable, but the only consumers of that appeared to
be kernel code which we control and not drivers.
TUNABLE_STR*() came along for free.
MFC: Remove the KMEMSTATS bogosity.2000-10-25T09:14:06ZPoul-Henning Kampphk@FreeBSD.org2000-10-25T09:14:06Zurn:sha1:142ba46c9014b52cdfbc11637936b5f54c21911a
MFC: Introduce M_ZERO
MFC:2000-07-07T14:15:20ZBoris Popovbp@FreeBSD.org2000-07-07T14:15:20Zurn:sha1:c72e366670c1eb037a5c6e33dc7da09c49396fc1
If kernel compiled with INVARIANTS clear all references to the removed
memory type and print warning message if not all memory of that
type is freed.
MFC: 1.65 Print "previous type" correctly when INVARIANTS is defined.2000-03-17T10:17:04ZPaul Saabps@FreeBSD.org2000-03-17T10:17:04Zurn:sha1:14dd88494c6d01adbe922a27a63abb9593388ddf Fix null-pointer dereference crash when the system is intentionally2000-02-16T21:11:33ZMatthew Dillondillon@FreeBSD.org2000-02-16T21:11:33Zurn:sha1:1f6889a1eb5070dfa739f4158cfb33f13b7a462d
run out of KVM through a mmap()/fork() bomb that allocates hundreds
of thousands of vm_map_entry structures.
Add panic to make null-pointer dereference crash a little more verbose.
Add a new sysctl, vm.max_proc_mmap, which specifies the maximum number
of mmap()'d spaces (discrete vm_map_entry's in the process). The value
defaults to around 9000 for a 128MB machine. The test is scaled for the
number of processes sharing a vmspace (aka linux threads). Setting
the value to 0 disables the feature.
PR: kern/16573
Approved by: jkh
Fixed sign and overflow bugs that caused the allocation size of the kernel2000-01-28T04:04:58ZDavid Greenmandg@FreeBSD.org2000-01-28T04:04:58Zurn:sha1:27b8623f218cd88db44e9644f2a230bc2f5b7568
malloc region (kmem_map) to be wrong and semi-random on systems with more
than 1GB of RAM. This is not a complete fix, but is sufficient for
machines with 4GB or less of memory. A complete fix will require some
changes to the getenv stuff so that 64bit values can be passed around.
NOT FIXED: machines with more than 4GB of RAM (e.g. some large Alphas)
since we're still using ints to hold some of the values.
Reviewed by: bde
KAME netinet6 basic part(no IPsec,no V6 Multicast Forwarding, no UDP/TCP1999-11-22T02:45:11ZYoshinobu Inoueshin@FreeBSD.org1999-11-22T02:45:11Zurn:sha1:82cd038d51e2fa970be77f4d59c56d3452fedec0
for IPv6 yet)
With this patch, you can assigne IPv6 addr automatically, and can reply to
IPv6 ping.
Reviewed by: freebsd-arch, cvs-committers
Obtained from: KAME project
Before we start to mess with the VFS name-cache clean things up a little bit:1999-10-03T12:18:29ZPoul-Henning Kampphk@FreeBSD.org1999-10-03T12:18:29Zurn:sha1:3b6fb88590bce72fcdbf17c09a593f5efb7bff24
Isolate the namecache in its own file, and give it a dedicated malloc type.