From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 53CB4C10DCE for ; Sun, 15 Mar 2020 21:53:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1D47A20674 for ; Sun, 15 Mar 2020 21:53:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729213AbgCOVxH (ORCPT ); Sun, 15 Mar 2020 17:53:07 -0400 Received: from mga03.intel.com ([134.134.136.65]:55823 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729166AbgCOVxH (ORCPT ); Sun, 15 Mar 2020 17:53:07 -0400 IronPort-SDR: tLh/jKg4Prg8JnI9DFlXnUE7jWi6TRX8aal4/WuHas6GFpwaL+/u0MiZk1ZalLSroNo71Jcux/ td3QI4Tj4uYw== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Mar 2020 14:53:05 -0700 IronPort-SDR: zEI9SkqgvTDcRFtXGlvFYgiWjoxf4mlZf2hoyvpMuskHqMd737tBaZ2OP06xT4S1uxCvuaqrBq 9ZiUosauTWQQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,558,1574150400"; d="scan'208";a="323318734" Received: from babayass-mobl.ger.corp.intel.com (HELO localhost) ([10.249.90.210]) by orsmga001.jf.intel.com with ESMTP; 15 Mar 2020 14:52:55 -0700 Date: Sun, 15 Mar 2020 23:52:53 +0200 From: Jarkko Sakkinen To: Waiman Long Cc: Eric Biggers , David Howells , James Morris , "Serge E. Hallyn" , Mimi Zohar , keyrings@vger.kernel.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-integrity@vger.kernel.org, Sumit Garg , Jerry Snitselaar , Roberto Sassu , Chris von Recklinghausen Subject: Re: [PATCH v3 3/3] KEYS: Use kvmalloc() to better handle large buffer allocation Message-ID: <20200315215253.GG224162@linux.intel.com> References: <20200313152102.1707-1-longman@redhat.com> <20200313152102.1707-4-longman@redhat.com> <20200313164306.GA907@sol.localdomain> <8f2f1787-88b0-f86d-991c-34cfd2f9b4aa@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8f2f1787-88b0-f86d-991c-34cfd2f9b4aa@redhat.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Sender: linux-integrity-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-integrity@vger.kernel.org On Fri, Mar 13, 2020 at 01:49:57PM -0400, Waiman Long wrote: > >> if (!tmpbuf || unlikely(ret > tmpbuflen)) { > >> if (unlikely(tmpbuf)) > >> - kzfree(tmpbuf); > >> + __kvzfree(tmpbuf, tmpbuflen); > > Both kzfree() and __kvzfree() handle a NULL pointer, so there's no need for the > > NULL check first. > > > I would like to keep this one because of the unlikely annotation. What (measurable) gain does it bring anyway? /Jarkko