From owner-freebsd-arch@freebsd.org Thu Jan 4 14:50:53 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F2B7EB9AFC; Thu, 4 Jan 2018 14:50:53 +0000 (UTC) (envelope-from srs0=fypj=d7=freebsd.org=kp@codepro.be) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E07526C91F; Thu, 4 Jan 2018 14:50:52 +0000 (UTC) (envelope-from srs0=fypj=d7=freebsd.org=kp@codepro.be) Received: from [172.16.2.10] (vega.codepro.be [IPv6:2a01:4f8:162:1127::3]) (Authenticated sender: kp) by venus.codepro.be (Postfix) with ESMTPSA id D24884506C; Thu, 4 Jan 2018 15:50:49 +0100 (CET) From: "Kristof Provost" To: freebsd-arch@freebsd.org Cc: freebsd-hackers , "FreeBSD Current" Subject: RFC: mallocarray() Date: Thu, 04 Jan 2018 15:51:09 +0100 X-Mailer: MailMate (2.0BETAr6102) Message-ID: <070C0DEB-E70C-42D9-B734-E0735A6C9B8E@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2018 14:50:53 -0000 Hi, I’d like to make it easier to avoid integer overflow issues in the kernel. It’d be a lot nicer to have a malloc function figure this out for us, so I’d like mallocarray(). https://reviews.freebsd.org/D13766 Are there any objections to this? Regards, Kristof