Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp43089ybt; Tue, 16 Jun 2020 16:02:20 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxQ4rHXKJS9Xcv9OfQIk71uKF0d2UXYWURCrsvCPTOu3HS+nVB6ZrTrW1qRjHwCAp8lwWxJ X-Received: by 2002:a17:906:76c4:: with SMTP id q4mr5162609ejn.371.1592348539904; Tue, 16 Jun 2020 16:02:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592348539; cv=none; d=google.com; s=arc-20160816; b=EMFg2mIK3V1TS+7AqCS6EIo2IY7MZnIcQK/BzpB4JOaRQ5BRQI6mXdcsx2GCx2jIbE ZjhKoxB7vDWsN2zurWy1kZqPVZaUnQYfGE21k7fTYYRtlN4wllPHELiV8SdhS9jGT0we ZLUFlut8qTGn4DxNNnFSwOffiFvVLpTA5IkeTABAgxNGsVsj4hlMZbApNpLGV5lgetVT dOchaz3ZcOLJ4req/CR3b9J8e41+um5Foex5FYJjKHA0xFvtntVFzp/YNUPjagKCojeU 5pFBl3BPOb3D/azdQfFeEGE//G7VP9SFNhDTXjqkFPdgvlGqZwc0IEtNZW7S46efzvZS ixJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :reply-to:message-id:subject:cc:to:from:date; bh=/G0ZZo+hfIsLY4Hx8Xvj+acWQVOIsMnCIbV4R2nkWQE=; b=Iv3WpM7HaPE7JnxqJvPgP0vWRunqn+K/EhVBZAGYEXi5eUo+rCrJWzQO+wlCk7U/Ep XTRnvc1qxvsAoVPriggEBii/sjSw3J7P9EVcM6tqvUbFiRFVQKNQPLiNKewMr9PykIZU StNqoinKWI2JRs5exPsN/YX+yppAfxYk/IjbywnUNx81YEkZD3bPYcG7MExNQ7vVlFgF eOoFdzJFAtA/QMEAnjtLYtQS1Xmt/6bl6RI0yhqx0Gig3n+/SwYyFbsv9OVPXYG12kyR rHHNEInFModCEcvjgSrhNs+qMEILbx6yywRUv8YDjFIAbQnvZ7Wr0tOKSweMNgnAvmYD Axdw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e7si11871366ejt.606.2020.06.16.16.01.54; Tue, 16 Jun 2020 16:02:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725941AbgFPXBs (ORCPT + 99 others); Tue, 16 Jun 2020 19:01:48 -0400 Received: from mx2.suse.de ([195.135.220.15]:39104 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725849AbgFPXBs (ORCPT ); Tue, 16 Jun 2020 19:01:48 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 6CB7AADA8; Tue, 16 Jun 2020 23:01:45 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id 1AC8EDA7C3; Wed, 17 Jun 2020 01:01:30 +0200 (CEST) Date: Wed, 17 Jun 2020 01:01:30 +0200 From: David Sterba To: Joe Perches Cc: Waiman Long , Andrew Morton , David Howells , Jarkko Sakkinen , James Morris , "Serge E. Hallyn" , Linus Torvalds , Matthew Wilcox , David Rientjes , Michal Hocko , Johannes Weiner , Dan Carpenter , David Sterba , "Jason A . Donenfeld" , linux-mm@kvack.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, linux-pm@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-amlogic@lists.infradead.org, linux-mediatek@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, linux-ppp@vger.kernel.org, wireguard@lists.zx2c4.com, linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org, linux-scsi@vger.kernel.org, target-devel@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-cifs@vger.kernel.org, linux-fscrypt@vger.kernel.org, ecryptfs@vger.kernel.org, kasan-dev@googlegroups.com, linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org, linux-sctp@vger.kernel.org, linux-nfs@vger.kernel.org, tipc-discussion@lists.sourceforge.net, linux-security-module@vger.kernel.org, linux-integrity@vger.kernel.org Subject: Re: [PATCH v4 0/3] mm, treewide: Rename kzfree() to kfree_sensitive() Message-ID: <20200616230130.GJ27795@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Joe Perches , Waiman Long , Andrew Morton , David Howells , Jarkko Sakkinen , James Morris , "Serge E. Hallyn" , Linus Torvalds , Matthew Wilcox , David Rientjes , Michal Hocko , Johannes Weiner , Dan Carpenter , "Jason A . Donenfeld" , linux-mm@kvack.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, linux-pm@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-amlogic@lists.infradead.org, linux-mediatek@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, linux-ppp@vger.kernel.org, wireguard@lists.zx2c4.com, linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org, linux-scsi@vger.kernel.org, target-devel@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-cifs@vger.kernel.org, linux-fscrypt@vger.kernel.org, ecryptfs@vger.kernel.org, kasan-dev@googlegroups.com, linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org, linux-sctp@vger.kernel.org, linux-nfs@vger.kernel.org, tipc-discussion@lists.sourceforge.net, linux-security-module@vger.kernel.org, linux-integrity@vger.kernel.org References: <20200616015718.7812-1-longman@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org On Tue, Jun 16, 2020 at 11:53:50AM -0700, Joe Perches wrote: > On Mon, 2020-06-15 at 21:57 -0400, Waiman Long wrote: > > v4: > > - Break out the memzero_explicit() change as suggested by Dan Carpenter > > so that it can be backported to stable. > > - Drop the "crypto: Remove unnecessary memzero_explicit()" patch for > > now as there can be a bit more discussion on what is best. It will be > > introduced as a separate patch later on after this one is merged. > > To this larger audience and last week without reply: > https://lore.kernel.org/lkml/573b3fbd5927c643920e1364230c296b23e7584d.camel@perches.com/ > > Are there _any_ fastpath uses of kfree or vfree? I'd consider kfree performance critical for cases where it is called under locks. If possible the kfree is moved outside of the critical section, but we have rbtrees or lists that get deleted under locks and restructuring the code to do eg. splice and free it outside of the lock is not always possible.