Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp669243ybh; Sat, 3 Aug 2019 07:21:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqzGELKGk20j/IRy3S/ZXMTgGcjRdkP6n7metaf2aa3N1TKXpmlBfgT2L+FQ6jaAM/aSog1x X-Received: by 2002:a63:eb06:: with SMTP id t6mr17970052pgh.107.1564842086945; Sat, 03 Aug 2019 07:21:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564842086; cv=none; d=google.com; s=arc-20160816; b=IcOFoQ3KeNTd7iZtPtZPF9G15l9b802m0CyqOrncFS04zCgnBJAcFN8ZKwmIb6d+FV gOx/j7VfuarrFLKRdJDO2S29HmdwJ3zjF7VcjAlA/QgIc3mMlFxEXnVAmA027dc0hH7Q y5gszugvt4XGuZWP9Z9Q59UWRivI0nnORpZ/Y3cymMn+nSTlWKdLuqBFxTmvK8TQ3y+y MPBs1h6rDzgbpr7LWECw0dKU2h//Rd60e7jCTels4WcJjKukfG3Ed4Zqm6p+k7W6qwxk NVBnvyUTWHU0WX74K97xV+rHiblzfGxhvwWKod8BeyfGSrxIQqtGGYUlQb3SCirosV23 z4Ag== 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:message-id:subject:cc :to:from:date; bh=GjasllrIC3Pnrz/9hYorEaiVodhbZPy+HxPX+i5Mb7U=; b=dqlgB4w6WNwoEo6cra+uSCsfC/wB1iQphREAmzic1eA8yJwiFu/J6fuXdc0P3gNlsE IYdBBJ6U/17/ptTbV9KpxYgp79XIWdn4liuvt5i1KdYg2XXOK2dJFT7OlihGz1riChvg WohQXnNlKRQO4fGG9dDPl9731YaHUOyX2uzLGLb880ZU8eZip4UeLkTqduspc7g7QrLe ZH5oikqses/vCbP66dDh8USToA9btsy1aFMW7CZXKLptqvFFbK+WuRl2g/yTL5AQ+LTh MAYkVvcsC7dtB56P0ZVyQlCE7/04lMZ+Y86cpsHvvGgGL/sCWbPQk5aMJA91Yso+xXOk HRcw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z13si9923148pgj.476.2019.08.03.07.21.09; Sat, 03 Aug 2019 07:21:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733176AbfHBOwm (ORCPT + 99 others); Fri, 2 Aug 2019 10:52:42 -0400 Received: from mx2.suse.de ([195.135.220.15]:57754 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2389271AbfHBOwm (ORCPT ); Fri, 2 Aug 2019 10:52:42 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 80E69AF3F; Fri, 2 Aug 2019 14:52:38 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id 09FD71E433B; Fri, 2 Aug 2019 16:52:27 +0200 (CEST) Date: Fri, 2 Aug 2019 16:52:27 +0200 From: Jan Kara To: Matthew Wilcox Cc: Jan Kara , Michal Hocko , john.hubbard@gmail.com, Andrew Morton , Christoph Hellwig , Dan Williams , Dave Chinner , Dave Hansen , Ira Weiny , Jason Gunthorpe , =?iso-8859-1?B?Suly9G1l?= Glisse , LKML , amd-gfx@lists.freedesktop.org, ceph-devel@vger.kernel.org, devel@driverdev.osuosl.org, devel@lists.orangefs.org, dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-block@vger.kernel.org, linux-crypto@vger.kernel.org, linux-fbdev@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-media@vger.kernel.org, linux-mm@kvack.org, linux-nfs@vger.kernel.org, linux-rdma@vger.kernel.org, linux-rpi-kernel@lists.infradead.org, linux-xfs@vger.kernel.org, netdev@vger.kernel.org, rds-devel@oss.oracle.com, sparclinux@vger.kernel.org, x86@kernel.org, xen-devel@lists.xenproject.org, John Hubbard Subject: Re: [PATCH 00/34] put_user_pages(): miscellaneous call sites Message-ID: <20190802145227.GQ25064@quack2.suse.cz> References: <20190802022005.5117-1-jhubbard@nvidia.com> <20190802091244.GD6461@dhcp22.suse.cz> <20190802124146.GL25064@quack2.suse.cz> <20190802142443.GB5597@bombadil.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190802142443.GB5597@bombadil.infradead.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Fri 02-08-19 07:24:43, Matthew Wilcox wrote: > On Fri, Aug 02, 2019 at 02:41:46PM +0200, Jan Kara wrote: > > On Fri 02-08-19 11:12:44, Michal Hocko wrote: > > > On Thu 01-08-19 19:19:31, john.hubbard@gmail.com wrote: > > > [...] > > > > 2) Convert all of the call sites for get_user_pages*(), to > > > > invoke put_user_page*(), instead of put_page(). This involves dozens of > > > > call sites, and will take some time. > > > > > > How do we make sure this is the case and it will remain the case in the > > > future? There must be some automagic to enforce/check that. It is simply > > > not manageable to do it every now and then because then 3) will simply > > > be never safe. > > > > > > Have you considered coccinele or some other scripted way to do the > > > transition? I have no idea how to deal with future changes that would > > > break the balance though. > > > > Yeah, that's why I've been suggesting at LSF/MM that we may need to create > > a gup wrapper - say vaddr_pin_pages() - and track which sites dropping > > references got converted by using this wrapper instead of gup. The > > counterpart would then be more logically named as unpin_page() or whatever > > instead of put_user_page(). Sure this is not completely foolproof (you can > > create new callsite using vaddr_pin_pages() and then just drop refs using > > put_page()) but I suppose it would be a high enough barrier for missed > > conversions... Thoughts? > > I think the API we really need is get_user_bvec() / put_user_bvec(), > and I know Christoph has been putting some work into that. That avoids > doing refcount operations on hundreds of pages if the page in question is > a huge page. Once people are switched over to that, they won't be tempted > to manually call put_page() on the individual constituent pages of a bvec. Well, get_user_bvec() is certainly a good API for one class of users but just looking at the above series, you'll see there are *many* places that just don't work with bvecs at all and you need something for those. Honza -- Jan Kara SUSE Labs, CR