From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58010 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231405AbiHOLnL (ORCPT ); Mon, 15 Aug 2022 07:43:11 -0400 Received: from mx0b-00069f02.pphosted.com (mx0b-00069f02.pphosted.com [205.220.177.32]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 280F524BF0 for ; Mon, 15 Aug 2022 04:43:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=date : from : to : cc : subject : message-id : references : content-type : in-reply-to : mime-version; s=corp-2022-7-12; bh=pxF7ZlnGhDpak8PF4jciRz4QyJaSrgKIa42q0hytEI8=; b=qf6m85xGKjxqTgChUM6c71VvNel8VgTo4+zx8gmiX3TeaBncdNc6ASp4VtAogSGYZ4m3 e57RyBzgn0Fh065w6j1qje0qCRooHZIVsdp3ER5GcGfjiRVOO6A+Awxk6xhkOflArFfj auaqTyiPKaxAUVESXm2Z3Xggk1ZcS1BGeUvSeiRn5hsilV97fN79wRQBpk/ZDp5Q+Q6W apKzd2ZnaXzjRhbYY5RvVaMcfQZlaI2BsrUTkFmGbTwPDRpxeKIVBP8l2yN9tKdC36M6 SXaJVODIKpPCBf6cEmVVJh6/YnU3iDTss9a0uk+JcchOOXygSnGSOQa/5kuVpELhr7Bw ug== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.onmicrosoft.com; s=selector2-oracle-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pxF7ZlnGhDpak8PF4jciRz4QyJaSrgKIa42q0hytEI8=; b=BrgWXmlUzmHBEcSGulMt6fdirURg9vV/X2riNGOden2BhdAfJki9SdXaACX/IsuuIKxI0eHRZGWxQXbeAmRiupD2SSBxAjdBi3ChVGngYcmJoxJALLULovfca25ic8MRKJqylfcnx40La8IOV/CC1DTdbOB+MeGB18S0fnODB7g= Date: Mon, 15 Aug 2022 14:42:49 +0300 From: Dan Carpenter Subject: Re: [PATCH] smatch_allocations: Give a hint about dma_alloc_(attrs|coherent) Message-ID: <20220815114249.GN3438@kadam> References: Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: MIME-Version: 1.0 List-ID: To: Christophe JAILLET Cc: smatch@vger.kernel.org On Mon, Aug 15, 2022 at 10:18:31AM +0200, Christophe JAILLET wrote: > In recent kernel, dma_alloc_attrs() and dma_alloc_coherent() zero the > allocated memory. > > Signed-off-by: Christophe JAILLET > --- > This was not the case in older kernel, so maybe it is better not to state > that the memory is zeroed. > > (I've not seen where/how this .zeroed information was used) This code is aspirational. I keep on creating lists of allocation functions but hopefully it can all be pulled into one central location. regards, dan carpenter