From: "Laba, SlawomirX" <slawomirx.laba@intel.com>
To: Alex Williamson <alex.williamson@redhat.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "alex.sierra@amd.com" <alex.sierra@amd.com>,
"willy@infradead.org" <willy@infradead.org>,
"hch@lst.de" <hch@lst.de>,
"Felix.Kuehling@amd.com" <Felix.Kuehling@amd.com>,
"apopple@nvidia.com" <apopple@nvidia.com>,
"david@redhat.com" <david@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2] mm: re-allow pinning of zero pfns (again)
Date: Fri, 26 Aug 2022 19:01:37 +0000 [thread overview]
Message-ID: <DM6PR11MB31137D5CBE5B38FA4BED564587759@DM6PR11MB3113.namprd11.prod.outlook.com> (raw)
In-Reply-To: <166015037385.760108.16881097713975517242.stgit@omen>
> Subject: [PATCH v2] mm: re-allow pinning of zero pfns (again)
>
> The below referenced commit makes the same error as 1c563432588d ("mm:
> fix is_pinnable_page against a cma page"), re-interpreting the logic to
> exclude pinning of the zero page, which breaks device assignment with vfio.
>
> To avoid further subtle mistakes, split the logic into discrete tests.
>
> Suggested-by: Matthew Wilcox <willy@infradead.org>
> Suggested-by: Felix Kuehling <felix.kuehling@amd.com>
> Link:
> https://lore.kernel.org/all/165490039431.944052.12458624139225785964.stgit
> @omen
> Fixes: f25cbb7a95a2 ("mm: add zone device coherent type memory
> support")
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
Tested-by: Slawomir Laba <slawomirx.laba@intel.com>
next prev parent reply other threads:[~2022-08-26 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 16:53 [PATCH v2] mm: re-allow pinning of zero pfns (again) Alex Williamson
2022-08-26 19:01 ` Laba, SlawomirX [this message]
2022-08-28 0:59 ` John Hubbard
2022-08-28 1:40 ` Andrew Morton
2022-08-28 12:37 ` Alex Williamson
2022-08-28 17:16 ` 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=DM6PR11MB31137D5CBE5B38FA4BED564587759@DM6PR11MB3113.namprd11.prod.outlook.com \
--to=slawomirx.laba@intel.com \
--cc=Felix.Kuehling@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alex.sierra@amd.com \
--cc=alex.williamson@redhat.com \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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: 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;
as well as URLs for NNTP newsgroup(s).