From: John Hubbard <jhubbard@nvidia.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Peter Xu <peterx@redhat.com>, Jason Gunthorpe <jgg@ziepe.ca>,
David Hildenbrand <david@redhat.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>, Jan Kara <jack@suse.cz>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH v3 1/4] mm: Fix invalid page pointer returned with FOLL_PIN gups
Date: Thu, 3 Feb 2022 13:13:51 -0800 [thread overview]
Message-ID: <012e78aa-fd4a-35c7-5405-752bcd675449@nvidia.com> (raw)
In-Reply-To: <YfvgC5Y9mTb3vKlV@infradead.org>
On 2/3/22 06:00, Christoph Hellwig wrote:
> On Thu, Feb 03, 2022 at 01:32:29AM -0800, John Hubbard wrote:
>> From: Peter Xu <peterx@redhat.com>
>>
>> Alex reported invalid page pointer returned with pin_user_pages_remote() from
>> vfio after upstream commit 4b6c33b32296 ("vfio/type1: Prepare for batched
>> pinning with struct vfio_batch"). This problem breaks NVIDIA vfio mdev.
>
> There still isn't any nvidia vfio mdev driver in the tree, so this
> changelog stilldoesn't make sense.
I'll remove that last sentence (and put in a tiny note that I'm scribbling
on Peter's commit description a little bit more), in order to avoid any
references to out of tree things.
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2022-02-03 21:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 9:32 [PATCH v3 0/4] mm/gup: some cleanups John Hubbard
2022-02-03 9:32 ` [PATCH v3 1/4] mm: Fix invalid page pointer returned with FOLL_PIN gups John Hubbard
2022-02-03 12:10 ` Claudio Imbrenda
2022-02-03 21:25 ` John Hubbard
2022-02-03 14:00 ` Christoph Hellwig
2022-02-03 21:13 ` John Hubbard [this message]
2022-02-03 9:32 ` [PATCH v3 2/4] mm/gup: clean up follow_pfn_pte() slightly John Hubbard
2022-02-03 13:31 ` Claudio Imbrenda
2022-02-03 20:53 ` John Hubbard
2022-02-03 13:53 ` Jan Kara
2022-02-03 15:01 ` Jason Gunthorpe
2022-02-03 15:18 ` Matthew Wilcox
2022-02-03 21:19 ` John Hubbard
2022-02-03 9:32 ` [PATCH v3 3/4] mm/gup: remove unused pin_user_pages_locked() John Hubbard
2022-02-03 11:52 ` Claudio Imbrenda
2022-02-03 9:32 ` [PATCH v3 4/4] mm/gup: remove get_user_pages_locked() John Hubbard
2022-02-03 12:04 ` Claudio Imbrenda
2022-02-03 14:01 ` Christoph Hellwig
2022-02-03 21:27 ` John Hubbard
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=012e78aa-fd4a-35c7-5405-752bcd675449@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=david@redhat.com \
--cc=hch@infradead.org \
--cc=imbrenda@linux.ibm.com \
--cc=jack@suse.cz \
--cc=jgg@ziepe.ca \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lukas.bulwahn@gmail.com \
--cc=peterx@redhat.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox