Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4331911ybi; Mon, 27 May 2019 16:15:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqw1zUBD2aNgezcgPziVmd93RfuoxDzbejX6Gq+trR9VFlNMHF8+wCL7tbCYiyDFcUx28A52 X-Received: by 2002:a17:90a:dd45:: with SMTP id u5mr1369895pjv.109.1558998914403; Mon, 27 May 2019 16:15:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558998914; cv=none; d=google.com; s=arc-20160816; b=Ogm8h48EGczxjcu/4IqheDqTg8RThoDqIVKuU0GGm2OKBxXlBW7gEe0AU46tOILRrD pL3wm6ScIbBFw5hTO+ncvaadR9ANOWp2VN//zAH3FL6zaPgRUQ50VwNwnSCwsFqyS3El Lho4CRhwpSX93RrQApGwfOeFYF0OZXpXKJBI0ffXZMBUOZ5hIqFrz9Slv4IzY1bY0om3 Q1u7EJLrBLG6jdPmslP9S1Ui2gRjhygwl8aqcrye9NJp9PafGt1xB4Nu9lY9aOp8ilQk xmTBzGzzDinOKD8i3U8lopldiwR1nwzUtsacFY6qA0M9tqmOyhjNrMdeSOuMmIn4xpjn 9V6w== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=wX6N01CkJjaDlOJ1ros8bm2onANhDW8NXyCYvkrtemg=; b=dfyEE+EzAwb9ew80DjiGlWaQeDgvzMQ9t2v/H8iH00nbIl4O6wy8TCXnPgmalSxszH rf8SwZD6mfWTni9uE8NfSK+NY52V/FALqwCMPRAqMsCH+QDae0tev7Cp+7UwVxpePk7/ sKbANHaoN28Olq1cEosVjZZoBeAwhgRai+HQ95/+NCb8zfrs0gAowWvcyiFnH5TpaOq8 Oi54e8Ze9H2KmfMkOxC6XD7ZAiucSTpABd1Omj65KOAOdKb3pVyLsOk9KNWKSOyRHOOp MyVqwUJkt537nK3vW1OE5ovgTPkqKIRzv8KNhGzBpDGtx8/SnkmeiepNFJY/zG4ipO7Q H1Sg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ziepe.ca header.s=google header.b=CZiPuQaE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-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 p13si19044130pgh.417.2019.05.27.16.14.58; Mon, 27 May 2019 16:15:14 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@ziepe.ca header.s=google header.b=CZiPuQaE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727509AbfE0XMn (ORCPT + 99 others); Mon, 27 May 2019 19:12:43 -0400 Received: from mail-vs1-f66.google.com ([209.85.217.66]:42933 "EHLO mail-vs1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727134AbfE0XMm (ORCPT ); Mon, 27 May 2019 19:12:42 -0400 Received: by mail-vs1-f66.google.com with SMTP id z11so11571891vsq.9 for ; Mon, 27 May 2019 16:12:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=wX6N01CkJjaDlOJ1ros8bm2onANhDW8NXyCYvkrtemg=; b=CZiPuQaEwv3lqb5SZe/gadbr2on0uyWsxhzjtp+toaxSYDJsJ0veJ+MsHzoIX193A5 tGyRL3+z39ibqHrkHL4ig8trKDTVq1uE+qiFVL+hYR3cMJo6o4Aspd5k9Fgs+fP8XTOZ EBxJZ1nObd0eaWg5uaSRpy2MVza2dQ+cCF/Qs41qm/fon5bRysCHkLJfqF4gN+OpH5zZ HsFELDr80DLkXDrbWdXyBCpSqjsGY+tiobrH4KQ86PlJi0KLZWAX8yW8dgduwngWgKtU Mr0WcxTALRjcOItn9ozWYXvUi+Rq2hQhmvWnN4sexsY5xyXZZ4wuDkWK4Q22BTIVNblW xkMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=wX6N01CkJjaDlOJ1ros8bm2onANhDW8NXyCYvkrtemg=; b=i+Z5dC2DPgTvJpYnKvp0eyPnBChtz3hkuZnDQ2s+v5j48wFbbOsMoUjYlpjhH6RNVu nvIGF1e8sWldr49NvvOb0aqKpD6ZX3O9yQAFTuenGG1qRDi7BlArQY3LBP4VL0WbbuP/ 0R0awTja97Yd4Mi6XR6HR/1XabiWjhfEbESwfB55D34PzhHEcHNrIls+EPkXeNN+cO7Y eUA/h4VJbqjC4iP4H4MZvPkfXDxPpG8PYcuKvZABA078XC6cmFIJg7pyP6HgyQRynqgz om4DvncKyT+orOwoObbB8MtAdfHuW5vIw0OkFqcqzn/lJ+SSA3z5tl+U2r4qJjjypuj6 5bdA== X-Gm-Message-State: APjAAAXQdvavJGr+Nen4tEr1+hgQtsRS20ATz6cZsRGLHunBP8UFGWvR AaMFrjUBERKD83c7BtpwlE0P2Q== X-Received: by 2002:a67:fa48:: with SMTP id j8mr50026871vsq.143.1558998761897; Mon, 27 May 2019 16:12:41 -0700 (PDT) Received: from ziepe.ca (hlfxns017vw-156-34-55-100.dhcp-dynamic.fibreop.ns.bellaliant.net. [156.34.55.100]) by smtp.gmail.com with ESMTPSA id a95sm5421589uaa.13.2019.05.27.16.12.41 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 27 May 2019 16:12:41 -0700 (PDT) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1hVOnI-000638-S7; Mon, 27 May 2019 20:12:40 -0300 Date: Mon, 27 May 2019 20:12:40 -0300 From: Jason Gunthorpe To: john.hubbard@gmail.com Cc: Andrew Morton , linux-mm@kvack.org, LKML , linux-rdma@vger.kernel.org, linux-fsdevel@vger.kernel.org, John Hubbard , Doug Ledford , Mike Marciniszyn , Dennis Dalessandro , Christian Benvenuti , Jan Kara , Ira Weiny , =?utf-8?B?SsOpcsO0bWU=?= Glisse Subject: Re: [PATCH v2] infiniband/mm: convert put_page() to put_user_page*() Message-ID: <20190527231240.GA23224@ziepe.ca> References: <20190525014522.8042-1-jhubbard@nvidia.com> <20190525014522.8042-2-jhubbard@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190525014522.8042-2-jhubbard@nvidia.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 24, 2019 at 06:45:22PM -0700, john.hubbard@gmail.com wrote: > From: John Hubbard > > For infiniband code that retains pages via get_user_pages*(), > release those pages via the new put_user_page(), or > put_user_pages*(), instead of put_page() > > This is a tiny part of the second step of fixing the problem described > in [1]. The steps are: > > 1) Provide put_user_page*() routines, intended to be used > for releasing pages that were pinned via get_user_pages*(). > > 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. > > 3) After (2) is complete, use get_user_pages*() and put_user_page*() to > implement tracking of these pages. This tracking will be separate from > the existing struct page refcounting. > > 4) Use the tracking and identification of these pages, to implement > special handling (especially in writeback paths) when the pages are > backed by a filesystem. Again, [1] provides details as to why that is > desirable. > > [1] https://lwn.net/Articles/753027/ : "The Trouble with get_user_pages()" > > Cc: Doug Ledford > Cc: Jason Gunthorpe > Cc: Mike Marciniszyn > Cc: Dennis Dalessandro > Cc: Christian Benvenuti > > Reviewed-by: Jan Kara > Reviewed-by: Dennis Dalessandro > Reviewed-by: Ira Weiny > Reviewed-by: Jérôme Glisse > Acked-by: Jason Gunthorpe > Tested-by: Ira Weiny > Signed-off-by: John Hubbard > --- > drivers/infiniband/core/umem.c | 7 ++++--- > drivers/infiniband/core/umem_odp.c | 10 +++++----- > drivers/infiniband/hw/hfi1/user_pages.c | 11 ++++------- > drivers/infiniband/hw/mthca/mthca_memfree.c | 6 +++--- > drivers/infiniband/hw/qib/qib_user_pages.c | 11 ++++------- > drivers/infiniband/hw/qib/qib_user_sdma.c | 6 +++--- > drivers/infiniband/hw/usnic/usnic_uiom.c | 7 ++++--- > 7 files changed, 27 insertions(+), 31 deletions(-) Applied to for-next, thanks Jason