| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | remove bad Pp; | jmc | 2023-04-17 | 1 | -3/+2 |
| | | | | | (sorry, otto, for not spotting in the updated diff) | ||||
| * | Dump (leak) info using utrace(2) and compile the code always in | otto | 2023-04-16 | 1 | -7/+17 |
| | | | | | | except for bootblocks. This way we have built-in leak detecction always (if enable by malloc flags). See man pages for details. | ||||
| * | Check all chunks in the delayed free list for write-after-free. | otto | 2023-04-01 | 1 | -3/+4 |
| | | | | | Should catch more of them and closer (in time) to the WAF. ok tb@ | ||||
| * | man pages: add missing commas between subordinate and main clauses | naddy | 2022-03-31 | 1 | -4/+4 |
| | | | | | | | | jmc@ dislikes a comma before "then" in a conditional, so leave those untouched. ok jmc@ | ||||
| * | Cache implementation has changed, we do not hold on to an exact number | otto | 2021-04-09 | 1 | -3/+4 |
| | | | | | of pages anymore, but also cache larger regions; ok tb@ | ||||
| * | - Make use of the fact that we know how the chunks are aligned, and | otto | 2021-02-25 | 1 | -3/+3 |
| | | | | | | | | | | | write 8 bytes at the time by using a uint64_t pointer. For an allocation a max of 4 such uint64_t's are written spread over the allocation. For pages sized and larger, the first page is junked in such a way. - Delayed free of a small chunk checks the corresponiding way. - Pages ending up in the cache are validated upon unmapping or re-use. In snaps for a while | ||||
| * | Add comment line saying S is described vaguely on purpose. | otto | 2019-09-14 | 1 | -2/+3 |
| | | | | | Prompted by guenther@ | ||||
| * | clarify that later flags modify earlier flags; | schwarze | 2019-05-19 | 1 | -2/+4 |
| | | | | | | triggered by a question from Jan Stary <hans at stare dot cz> on misc@; OK otto@ | ||||
| * | Mention introduction of *_conceal. | otto | 2019-05-13 | 1 | -2/+8 |
| | | |||||
| * | Inroduce malloc_conceal() and calloc_conceal(). Similar to their | otto | 2019-05-10 | 1 | -3/+26 |
| | | | | | | counterparts but return memory in pages marked MAP_CONCEAL and on free() freezero() is actually called. | ||||
| * | remove a stray line accidentally left behind in rev. 1.120; | schwarze | 2018-12-05 | 1 | -3/+2 |
| | | | | | patch from Hiltjo Posthuma <hiltjo at codemadness dot org> | ||||
| * | fold the contents of malloc.conf.5 into malloc.3 and sysctl.2, | jmc | 2018-11-21 | 1 | -6/+118 |
| | | | | | | | now that there is essentially no malloc.conf; text tweaked by deraadt; ok otto deraadt | ||||
| * | Introducing malloc_usable_size() was a mistake. While some other | otto | 2018-11-21 | 1 | -27/+4 |
| | | | | | | | | | | | | 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 | ||||
| * | Implement malloc_usable_size(); ok millert@ deraadt@ and jmc@ for the man page | otto | 2018-11-18 | 1 | -5/+29 |
| | | |||||
| * | zap last remains of malloc.conf; prompted by and ok jmc@ | otto | 2018-11-08 | 1 | -6/+6 |
| | | |||||
| * | rm FILES section; prompted by Janne Johansson | otto | 2018-11-06 | 1 | -7/+2 |
| | | |||||
| * | Implement C11's aligned_alloc(3). ok guenther@ | otto | 2018-11-05 | 1 | -4/+41 |
| | | |||||
| * | Typo: freezeo -> freezero | tb | 2017-05-15 | 1 | -3/+3 |
| | | | | | From "fenderq" on freenode via tj@ | ||||
| * | Rearrange text a bit to make it clear what "discarded" means; ok jmc@ deraadt@ | otto | 2017-04-23 | 1 | -8/+13 |
| | | |||||
| * | consictently use .Dv NULL and a few other tweaks; ok schwarze@ | otto | 2017-04-17 | 1 | -20/+17 |
| | | |||||
| * | allow clearing less than allocated and document freezero(3) better | otto | 2017-04-13 | 1 | -8/+21 |
| | | |||||
| * | tweak previous; | jmc | 2017-04-10 | 1 | -4/+4 |
| | | |||||
| * | Introducing freezero(3) a version of free that guarantees the process | otto | 2017-04-10 | 1 | -24/+58 |
| | | | | | | | no longer has access to the content of a memmory object. It does this by either clearing (if the object memory remains cached) or by calling munmap(2). ok millert@, deraadt@, guenther@ | ||||
| * | Consistentcy between nmembers and size order. From Christopher Hettrick; | otto | 2017-04-06 | 1 | -8/+8 |
| | | | | | ok deraadt@ | ||||
| * | rephrase more enumerations of functions | otto | 2017-03-29 | 1 | -13/+10 |
| | | |||||
| * | Stop enumeration all allocation functions, just say "allocation functions"libressl-v2.5.2 | otto | 2017-03-26 | 1 | -32/+13 |
| | | | | | ok jmc@ deraadt@ | ||||
| * | document new recallocarray diagnostic; zap a few diagnostics that should | otto | 2017-03-24 | 1 | -8/+9 |
| | | | | | never occur | ||||
| * | remove unneccessary macro; | jmc | 2017-03-17 | 1 | -2/+2 |
| | | |||||
| * | Strengthen description of recallocarray(3) behaviour, hoping that readers | deraadt | 2017-03-17 | 1 | -5/+10 |
| | | | | | | make the behaviour -> use case connection. help from jmc and jsing | ||||
| * | Some tweaks from jmc@ and describe better what recallocarray does; | otto | 2017-03-07 | 1 | -7/+16 |
| | | | | | help and ok from tom@ and deraadt@ | ||||
| * | Introducing recallocarray(3), a blend of calloc(3) and reallocarray(3) | otto | 2017-03-06 | 1 | -6/+64 |
| | | | | | | with the added feature that released memory is cleared. Much input from various developers. ok deraadt@ tom@ | ||||
| * | malloc does not *need* to return page-aligned objects for size >= | otto | 2017-02-12 | 1 | -5/+2 |
| | | | | | | a page. This is not required by any standard and other malloc implementation do not document (or implement) this. ok deraadt@ | ||||
| * | avoid sentence splicing; | jmc | 2016-10-20 | 1 | -2/+2 |
| | | |||||
| * | canary corruption message changed a bit | otto | 2016-10-20 | 1 | -5/+5 |
| | | |||||
| * | make clear the length printed is the requested length | otto | 2016-10-08 | 1 | -3/+3 |
| | | |||||
| * | grammar fix previous; | jmc | 2016-10-07 | 1 | -2/+2 |
| | | |||||
| * | document "chunk canary corrupted" error | otto | 2016-10-07 | 1 | -2/+7 |
| | | |||||
| * | Document ``use after free'' error message | otto | 2016-04-03 | 1 | -2/+4 |
| | | |||||
| * | Remove sentences in RETURN VALUES sections saying that functions with | mmcc | 2016-03-12 | 1 | -6/+2 |
| | | | | | | | | | | | | | | void return types 'return no value'. This is obvious and therefore unneccessary to mention. We spare rewind(3)'s sentence because espie@ pointed out that it's a warning - the function masks a potential error. This commit also adds a sentence to X509_free clarifying that it's NULL-safe. This bit was discussed with doug@. ok martijn@, sentiment supported by schwarze@ | ||||
| * | Fix err(3) calls after allocation failures in examples. | schwarze | 2016-02-05 | 1 | -8/+8 |
| | | | | | | | There is long-standing consensus that err(1, NULL) is the best idiom after failure of malloc(3) and friends. Quirk in the manual noticed by tb@. | ||||
| * | Long ago, malloc internally had two kinds of failures, warnings and errors. | tedu | 2016-01-06 | 1 | -6/+3 |
| | | | | | | | | | The 'A' option elevated warnings to errors, and has been the default for some time. Then warnings were effectively eliminated in favor of everything being an error, but then the 'a' flag turned real errors into warnings! Remove the 'a' option entirely. You shouldn't have used it anyway. ok tb tdeval | ||||
| * | use .Va for global variables, and .Vt where the type is included | schwarze | 2015-09-14 | 1 | -4/+3 |
| | | |||||
| * | remove incorrect statement. the standard *does* require calloc to check | tedu | 2015-03-14 | 1 | -7/+2 |
| | | | | | | for overflow. stop talking about old broken systems, there's little use for such info. | ||||
| * | missing , found by Dongsheng Song | deraadt | 2015-01-08 | 1 | -3/+3 |
| | | |||||
| * | fix NAME; | jmc | 2014-12-09 | 1 | -3/+3 |
| | | |||||
| * | remove cfree from documentation | tedu | 2014-12-08 | 1 | -19/+3 |
| | | |||||
| * | malloc(3) is in the "comp" install set, malloc.conf(5) in "man", | schwarze | 2014-12-06 | 1 | -126/+8 |
| | | | | | | | breaking the hardlink between file system entries, confusing apropos(1). Split malloc.conf(5) out of malloc(3) as suggested by deraadt@. Feedback and OK jmc@, OK deraadt@ tedu@ jasper@. | ||||
| * | clean up verbiage around the calculations; ok ingo jmc otto | deraadt | 2014-10-30 | 1 | -5/+5 |
| | | |||||
| * | Don't mention old systems where realloc(NULL, n) didn't work as we | millert | 2014-10-30 | 1 | -11/+7 |
| | | | | | | don't want to give people the idea that this is non-portable (it has been present since C89). OK deraadt@ schwarze@ | ||||
| * | Save space in man page: err() -> errc() and combine vars. | doug | 2014-10-23 | 1 | -18/+11 |
| | | | | | | | Suggested by millert@ and schwarze@. OK schwarze@, millert@ | ||||
 |
index : openbsd | |
| A mirror of https://github.com/libressl/openbsd.git |
| summaryrefslogtreecommitdiff |