<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libc/stdlib/malloc.c, branch OPENBSD_6_8_BASE</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=OPENBSD_6_8_BASE</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=OPENBSD_6_8_BASE'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2020-09-06T06:41:03+00:00</updated>
<entry>
<title>For page-sized and larger allocations do not put the pages we're</title>
<updated>2020-09-06T06:41:03+00:00</updated>
<author>
<name>otto</name>
<email></email>
</author>
<published>2020-09-06T06:41:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=764cad0b41a6709d8db171bee28134987f460c1a'/>
<id>urn:sha1:764cad0b41a6709d8db171bee28134987f460c1a</id>
<content type='text'>
shaving off into the cache but unamp them. Pages in the cache get
re-used and then a future grow of the first allocation will be
hampered. Also make realloc a no-op for small shrinkage.
ok deraadt@
</content>
</entry>
<entry>
<title>When system calls indicate an error they return -1, not some arbitrary</title>
<updated>2019-06-28T13:35:02+00:00</updated>
<author>
<name>deraadt</name>
<email></email>
</author>
<published>2019-06-28T13:35:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=835d788017c49be8b4986b0f04686da55f2cd0da'/>
<id>urn:sha1:835d788017c49be8b4986b0f04686da55f2cd0da</id>
<content type='text'>
value &lt; 0.  errno is only updated in this case.  Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
</content>
</entry>
<entry>
<title>Only override size of chunk if we're not given the actual length.</title>
<updated>2019-05-23T06:43:18+00:00</updated>
<author>
<name>otto</name>
<email></email>
</author>
<published>2019-05-23T06:43:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=1deffb2f6064562c73be679de4e1df2baa39ea0d'/>
<id>urn:sha1:1deffb2f6064562c73be679de4e1df2baa39ea0d</id>
<content type='text'>
Fixes malloc_conceal...freezero with malloc options C and/or G.
</content>
</entry>
<entry>
<title>Inroduce malloc_conceal() and calloc_conceal(). Similar to their</title>
<updated>2019-05-10T15:03:24+00:00</updated>
<author>
<name>otto</name>
<email></email>
</author>
<published>2019-05-10T15:03:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=5110d9a926df971b8571a962d563e7d569b505d7'/>
<id>urn:sha1:5110d9a926df971b8571a962d563e7d569b505d7</id>
<content type='text'>
counterparts but return memory in pages marked MAP_CONCEAL and on
free() freezero() is actually called.
</content>
</entry>
<entry>
<title>Move default numer of pools in the multi-threaded case to 8. Various tests</title>
<updated>2019-01-10T18:47:05+00:00</updated>
<author>
<name>otto</name>
<email></email>
</author>
<published>2019-01-10T18:47:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=d88d3b118149ad760df4de56ee7551bd1616395e'/>
<id>urn:sha1:d88d3b118149ad760df4de56ee7551bd1616395e</id>
<content type='text'>
by me and others indicate that it is the optimum.
</content>
</entry>
<entry>
<title>Make the "not my pool" searching loop a tiny bit smarter, while</title>
<updated>2019-01-10T18:45:33+00:00</updated>
<author>
<name>otto</name>
<email></email>
</author>
<published>2019-01-10T18:45:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=93282eac7fa28695cb6880305f3757cbff94eca0'/>
<id>urn:sha1:93282eac7fa28695cb6880305f3757cbff94eca0</id>
<content type='text'>
making the number of pools variable.  Do not document the malloc
conf settings atm, don't know yet if they will stay.  Thanks to all
the testers. ok deraadt@
</content>
</entry>
<entry>
<title>Improve speed for the multi-threaded case by reducing lock contention.</title>
<updated>2018-12-10T07:57:49+00:00</updated>
<author>
<name>otto</name>
<email></email>
</author>
<published>2018-12-10T07:57:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=e0a6e1a675a8779862b6efd50bfae854b7e5ec92'/>
<id>urn:sha1:e0a6e1a675a8779862b6efd50bfae854b7e5ec92</id>
<content type='text'>
tested by many; ok florian@
</content>
</entry>
<entry>
<title>style; OK otto</title>
<updated>2018-12-09T11:32:02+00:00</updated>
<author>
<name>florian</name>
<email></email>
</author>
<published>2018-12-09T11:32:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=f73e08ba21e8fc91965e6f4f7223f9b4ecf5ae70'/>
<id>urn:sha1:f73e08ba21e8fc91965e6f4f7223f9b4ecf5ae70</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Refactor "find the right pool" code into a function. ok djm@ tb@</title>
<updated>2018-11-27T17:29:55+00:00</updated>
<author>
<name>otto</name>
<email></email>
</author>
<published>2018-11-27T17:29:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=df589015ce8498eea97628dcddf139bf3983e3bf'/>
<id>urn:sha1:df589015ce8498eea97628dcddf139bf3983e3bf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Introducing malloc_usable_size() was a mistake. While some other</title>
<updated>2018-11-21T06:57:04+00:00</updated>
<author>
<name>otto</name>
<email></email>
</author>
<published>2018-11-21T06:57:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=a945275c9231635eb80ae0051017756c9e083b37'/>
<id>urn:sha1:a945275c9231635eb80ae0051017756c9e083b37</id>
<content type='text'>
libs have it, it is a function that is considered harmful, so:

Delete malloc_usable_size(). It is a function that blurs the line
between malloc managed memory and application managed memory and
exposes some of the internal workings of malloc.  If an application
relies on that, it is likely to break using another implementation
of malloc.  If you want usable size x, just allocate x bytes. ok
deraadt@ and other devs
</content>
</entry>
</feed>
