From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: linux-next: manual merge of the vfs tree with the ext4 tree Date: Tue, 14 Apr 2015 22:14:56 +0100 Message-ID: <20150414211456.GH889@ZenIV.linux.org.uk> References: <20150414113025.06905c2a@canb.auug.org.au> <20150414014855.GU889@ZenIV.linux.org.uk> <20150414170000.GB29810@thunk.org> <20150414171743.GC889@ZenIV.linux.org.uk> <20150414210215.GD29810@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:60823 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754971AbbDNVPB (ORCPT ); Tue, 14 Apr 2015 17:15:01 -0400 Content-Disposition: inline In-Reply-To: <20150414210215.GD29810@thunk.org> Sender: linux-next-owner@vger.kernel.org List-ID: To: Theodore Ts'o , Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, David Howells On Tue, Apr 14, 2015 at 05:02:15PM -0400, Theodore Ts'o wrote: > On Tue, Apr 14, 2015 at 06:17:43PM +0100, Al Viro wrote: > > Except that you do not handle the slow unencrypted case - you end up with > > kfree() on the freshly kunmaped address. > > Ah, right, we're actually kmalloc'ing the space that case as well --- > so hanging on the cpage is pointless; which was the point you were > making. Sorry, I was being slow. > > So what we have works, but it's not optimal. Will fix. BTW, take a look at kfree_put_link(); no need to reinvent that wheel...