openbsd/src/lib/libc, branch libressl-v2.5.2 A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=libressl-v2.5.2 2017-03-26T09:21:33+00:00 Stop enumeration all allocation functions, just say "allocation functions" 2017-03-26T09:21:33+00:00 otto 2017-03-26T09:21:33+00:00 urn:sha1:ec59f40a3b14e190dc7b190e492cf63cdb1c8628 ok jmc@ deraadt@ add a helper function to print all pools #ifdef MALLOC_STATS 2017-03-24T16:23:05+00:00 otto 2017-03-24T16:23:05+00:00 urn:sha1:461d6ff4a5d26a1f9df33d390c4adf991ae10616 from David CARLIER document new recallocarray diagnostic; zap a few diagnostics that should 2017-03-24T16:17:50+00:00 otto 2017-03-24T16:17:50+00:00 urn:sha1:fdf371b4345601ade1791e202a6db6eeb03aa86e never occur move recallocarray to malloc.c and 2017-03-24T16:15:31+00:00 otto 2017-03-24T16:15:31+00:00 urn:sha1:46f72410b43cd5a1ff1d3da7bb4a7b291baf244b - use internal meta-data to do more consistency checking (especially with option C) - use cheap free if possible ok deraadt@ remove unneccessary macro; 2017-03-17T18:33:04+00:00 jmc 2017-03-17T18:33:04+00:00 urn:sha1:e544d3375a158284535329d0e6e1f7e1151f6e7b Strengthen description of recallocarray(3) behaviour, hoping that readers 2017-03-17T17:00:38+00:00 deraadt 2017-03-17T17:00:38+00:00 urn:sha1:39dae6bdc1f4322df23a553b4f3dd1b9e4a7d1b3 make the behaviour -> use case connection. help from jmc and jsing Some tweaks from jmc@ and describe better what recallocarray does; 2017-03-07T06:07:50+00:00 otto 2017-03-07T06:07:50+00:00 urn:sha1:cfcfab851673299bea759c10bc1fac9d1cc1c204 help and ok from tom@ and deraadt@ Introducing recallocarray(3), a blend of calloc(3) and reallocarray(3) 2017-03-06T18:44:21+00:00 otto 2017-03-06T18:44:21+00:00 urn:sha1:0dbf4a31aa2becc157a25e82d3291c6494b3667e with the added feature that released memory is cleared. Much input from various developers. ok deraadt@ tom@ size is unsigned so using ==0 not <=0 when checking for buffer exhaustion 2017-03-06T18:16:27+00:00 millert 2017-03-06T18:16:27+00:00 urn:sha1:ff039d35a200670887f77531569823a1886c89af Pull in a change from the bind 8 resolver that fixes a potential 2017-03-06T18:14:41+00:00 millert 2017-03-06T18:14:41+00:00 urn:sha1:1baf267ffff48256f940f576b0151fa86e33fb0d crash when given a large hex number as part of the dotted quad. OK deraadt@ jsg@