From mboxrd@z Thu Jan 1 00:00:00 1970 From: Waiman Long Subject: Re: [PATCH v4 2/3] mm, treewide: Rename kzfree() to kfree_sensitive() Date: Tue, 16 Jun 2020 11:05:59 -0400 Message-ID: <72aa954d-4933-333c-b784-f8df14e407e6@redhat.com> References: <20200616015718.7812-1-longman@redhat.com> <20200616015718.7812-3-longman@redhat.com> <20200616142624.GO4282@kadam> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20200616142624.GO4282@kadam> Content-Language: en-US Sender: target-devel-owner@vger.kernel.org To: Dan Carpenter Cc: Andrew Morton , David Howells , Jarkko Sakkinen , James Morris , "Serge E. Hallyn" , Linus Torvalds , Joe Perches , Matthew Wilcox , David Rientjes , Michal Hocko , Johannes Weiner , 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@l List-Id: virtualization@lists.linuxfoundation.org On 6/16/20 10:26 AM, Dan Carpenter wrote: > Last time you sent this we couldn't decide which tree it should go > through. Either the crypto tree or through Andrew seems like the right > thing to me. > > Also the other issue is that it risks breaking things if people add > new kzfree() instances while we are doing the transition. Could you > just add a "#define kzfree kfree_sensitive" so that things continue to > compile and we can remove it in the next kernel release? > > regards, > dan carpenter > Yes, that make sure sense. Will send out v5 later today. Cheers, Longman