From: John Hubbard <jhubbard@nvidia.com> To: Jan Kara <jack@suse.cz> Cc: Jason Gunthorpe <jgg@ziepe.ca>, Andrew Morton <akpm@linux-foundation.org>, john.hubbard@gmail.com, Matthew Wilcox <willy@infradead.org>, Michal Hocko <mhocko@kernel.org>, Christopher Lameter <cl@linux.com>, Dan Williams <dan.j.williams@intel.com>, linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>, linux-rdma <linux-rdma@vger.kernel.org>, linux-fsdevel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>, Jerome Glisse <jglisse@redhat.com>, Christoph Hellwig <hch@infradead.org>, Ralph Campbell <rcampbell@nvidia.com> Subject: Re: [PATCH v4 2/3] mm: introduce put_user_page*(), placeholder versions Date: Sun, 4 Nov 2018 23:25:31 -0800 [thread overview] Message-ID: <4f47f3d4-1b00-e534-309c-7fb044337040@nvidia.com> (raw) In-Reply-To: <20181018101951.GO23493@quack2.suse.cz> On 10/18/18 3:19 AM, Jan Kara wrote: > On Thu 11-10-18 20:53:34, John Hubbard wrote: >> On 10/11/18 6:23 PM, John Hubbard wrote: >>> On 10/11/18 6:20 AM, Jason Gunthorpe wrote: >>>> On Thu, Oct 11, 2018 at 10:49:29AM +0200, Jan Kara wrote: [...] > Well, put_page() cannot assert page is not dma-pinned as someone can still > to get_page(), put_page() on dma-pinned page and that must not barf. But > put_page() could assert that if the page is pinned, refcount is >= > pincount. That will detect leaked pin references relatively quickly. > That assertion is definitely a life saver. I've been attempting a combination of finishing up more call site conversions, and runtime testing, and this lights up the missing conversions pretty nicely. As I mentioned in another thread just now, I'll send out an updated RFC this week, so that people can look through it well before the LPC (next week). thanks, -- John Hubbard NVIDIA
WARNING: multiple messages have this Message-ID (diff)
From: John Hubbard <jhubbard@nvidia.com> To: Jan Kara <jack@suse.cz> Cc: Jason Gunthorpe <jgg@ziepe.ca>, Andrew Morton <akpm@linux-foundation.org>, <john.hubbard@gmail.com>, Matthew Wilcox <willy@infradead.org>, Michal Hocko <mhocko@kernel.org>, Christopher Lameter <cl@linux.com>, Dan Williams <dan.j.williams@intel.com>, <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>, linux-rdma <linux-rdma@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>, Al Viro <viro@zeniv.linux.org.uk>, "Jerome Glisse" <jglisse@redhat.com>, Christoph Hellwig <hch@infradead.org>, "Ralph Campbell" <rcampbell@nvidia.com> Subject: Re: [PATCH v4 2/3] mm: introduce put_user_page*(), placeholder versions Date: Sun, 4 Nov 2018 23:25:31 -0800 [thread overview] Message-ID: <4f47f3d4-1b00-e534-309c-7fb044337040@nvidia.com> (raw) In-Reply-To: <20181018101951.GO23493@quack2.suse.cz> On 10/18/18 3:19 AM, Jan Kara wrote: > On Thu 11-10-18 20:53:34, John Hubbard wrote: >> On 10/11/18 6:23 PM, John Hubbard wrote: >>> On 10/11/18 6:20 AM, Jason Gunthorpe wrote: >>>> On Thu, Oct 11, 2018 at 10:49:29AM +0200, Jan Kara wrote: [...] > Well, put_page() cannot assert page is not dma-pinned as someone can still > to get_page(), put_page() on dma-pinned page and that must not barf. But > put_page() could assert that if the page is pinned, refcount is >= > pincount. That will detect leaked pin references relatively quickly. > That assertion is definitely a life saver. I've been attempting a combination of finishing up more call site conversions, and runtime testing, and this lights up the missing conversions pretty nicely. As I mentioned in another thread just now, I'll send out an updated RFC this week, so that people can look through it well before the LPC (next week). thanks, -- John Hubbard NVIDIA
next prev parent reply other threads:[~2018-11-05 7:25 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-08 21:16 [PATCH v4 0/3] get_user_pages*() and RDMA: first steps john.hubbard 2018-10-08 21:16 ` [PATCH v4 1/3] mm: get_user_pages: consolidate error handling john.hubbard 2018-10-09 0:05 ` Andrew Morton 2018-10-08 21:16 ` [PATCH v4 2/3] mm: introduce put_user_page*(), placeholder versions john.hubbard 2018-10-09 0:14 ` Andrew Morton 2018-10-09 8:30 ` Jan Kara 2018-10-09 23:20 ` Andrew Morton 2018-10-10 0:32 ` John Hubbard 2018-10-10 0:32 ` John Hubbard 2018-10-10 23:43 ` Andrew Morton 2018-10-10 23:43 ` Andrew Morton 2018-10-10 0:42 ` John Hubbard 2018-10-10 0:42 ` John Hubbard 2018-10-10 8:59 ` Jan Kara 2018-10-10 23:23 ` John Hubbard 2018-10-10 23:23 ` John Hubbard 2018-10-11 8:42 ` Jan Kara 2018-10-10 23:45 ` Andrew Morton 2018-10-10 23:45 ` Andrew Morton 2018-10-11 8:49 ` Jan Kara 2018-10-11 13:20 ` Jason Gunthorpe 2018-10-12 1:23 ` John Hubbard 2018-10-12 1:23 ` John Hubbard 2018-10-12 3:53 ` John Hubbard 2018-10-12 3:53 ` John Hubbard 2018-10-18 10:19 ` Jan Kara 2018-11-05 7:25 ` John Hubbard [this message] 2018-11-05 7:25 ` John Hubbard 2018-10-22 19:43 ` Jason Gunthorpe 2018-11-05 7:17 ` John Hubbard 2018-11-05 7:17 ` John Hubbard 2018-11-05 8:37 ` Jan Kara 2018-10-08 21:16 ` [PATCH v4 3/3] infiniband/mm: convert put_page() to put_user_page*() john.hubbard 2018-10-09 9:52 ` kbuild test robot
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4f47f3d4-1b00-e534-309c-7fb044337040@nvidia.com \ --to=jhubbard@nvidia.com \ --cc=akpm@linux-foundation.org \ --cc=cl@linux.com \ --cc=dan.j.williams@intel.com \ --cc=hch@infradead.org \ --cc=jack@suse.cz \ --cc=jgg@ziepe.ca \ --cc=jglisse@redhat.com \ --cc=john.hubbard@gmail.com \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-rdma@vger.kernel.org \ --cc=mhocko@kernel.org \ --cc=rcampbell@nvidia.com \ --cc=viro@zeniv.linux.org.uk \ --cc=willy@infradead.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.