From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 1453 invoked from network); 21 Jul 2020 18:58:26 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 21 Jul 2020 18:58:26 -0000 Received: (qmail 30126 invoked by uid 550); 21 Jul 2020 18:58:22 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 30104 invoked from network); 21 Jul 2020 18:58:22 -0000 From: Florian Weimer To: Rich Felker Cc: Ariadne Conill , musl@lists.openwall.com References: <3289935.7VNl89jVkd@localhost> <20200721183945.GQ14669@brightrain.aerifal.cx> Date: Tue, 21 Jul 2020 20:58:04 +0200 In-Reply-To: <20200721183945.GQ14669@brightrain.aerifal.cx> (Rich Felker's message of "Tue, 21 Jul 2020 14:39:46 -0400") Message-ID: <87pn8or8zn.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [musl] perhaps we should add re[c]allocarray? * Rich Felker: > recallocarray presumably needs to zero the new part which means it > needs to know the old exact size, which means it depends on having > either knowledge of implementation internals or a working, exact > malloc_usable_size (AFAIK all legacy/existing ones except musl > mallocng are broken and return a value greater than the originally > allocated size). The caller has to pass the old member count to recallocarray, in an additional argument. I think this avoids this particular issue, and also makes it easy to achive interposition-safety.