From: Peter Xu <peterx@redhat.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: Mina Almasry <almasrymina@google.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Linux-MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm, hugetlb: fix resv_huge_pages underflow on UFFDIO_COPY
Date: Fri, 14 May 2021 15:16:36 -0400 [thread overview]
Message-ID: <YJ7MlJaYzzJ/01R1@t490s> (raw)
In-Reply-To: <dd83c970-797e-6b7a-194d-790df5d53867@oracle.com>
On Fri, May 14, 2021 at 10:56:36AM -0700, Mike Kravetz wrote:
> Since this is a shared mapping, can we not have a 'regular' mapping to
> the same range that is uffd registered? And, that regular mappings could
> fault and race with the uffd copy code?
Yeah we can.. Please ignore the paragraph in the parenthesis. Sorry.
--
Peter Xu
next prev parent reply other threads:[~2021-05-14 19:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 23:43 Mina Almasry
2021-05-13 23:49 ` Mina Almasry
2021-05-14 0:14 ` Mike Kravetz
2021-05-14 0:23 ` Mina Almasry
2021-05-14 4:02 ` Mike Kravetz
2021-05-14 12:31 ` Peter Xu
2021-05-14 17:56 ` Mike Kravetz
2021-05-14 18:30 ` Axel Rasmussen
2021-05-14 19:16 ` Peter Xu [this message]
2021-05-20 19:18 ` Mina Almasry
2021-05-20 19:21 ` Mina Almasry
2021-05-20 20:00 ` Mike Kravetz
2021-05-20 20:31 ` Mina Almasry
2021-05-21 2:05 ` Mina Almasry
-- strict thread matches above, loose matches on Subject: below --
2021-05-12 3:06 resv_huge_page underflow with userfaultfd test Mike Kravetz
[not found] ` <20210512065813.89270-1-almasrymina@google.com>
2021-05-12 7:44 ` [PATCH] mm, hugetlb: fix resv_huge_pages underflow on UFFDIO_COPY Mina Almasry
[not found] ` <CAJHvVch0ZMapPVEc0Ge5V4KDgNDNhECbqwDi0y9XxsxFXQZ-gg@mail.gmail.com>
[not found] ` <c455d241-11f6-95a6-eb29-0ddd94eedbd7@oracle.com>
2021-05-12 19:42 ` Mina Almasry
2021-05-12 20:14 ` Peter Xu
2021-05-12 21:31 ` Mike Kravetz
2021-05-12 21:52 ` Mina Almasry
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=YJ7MlJaYzzJ/01R1@t490s \
--to=peterx@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.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