From: Mina Almasry <almasrymina@google.com>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
Linux-MM <linux-mm@kvack.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Peter Xu <peterx@redhat.com>
Subject: Re: resv_huge_page underflow with userfaultfd test
Date: Tue, 11 May 2021 00:08:56 -0700 [thread overview]
Message-ID: <CAHS8izPvx0WzK5C+NWvWPRqvb1OWABv8_FvOcDS+L+5gvz6D2Q@mail.gmail.com> (raw)
In-Reply-To: <CAJHvVcg-eK4Z74AOtsUMafQ5AyWV0Ad0OHRzR6vLvn-80maQ1g@mail.gmail.com>
On Mon, May 10, 2021 at 11:46 PM Axel Rasmussen
<axelrasmussen@google.com> wrote:
>
> Thanks for the investigation, Mike!
>
> Mina, since hugetlb_mcopy_atomic_pte is specific to userfaultfd, I'm
> happy to take a deeper look at it this week as well.
>
> For context, we have seen the WARN_ON Mina described trigger in
> production before, but were never able to reproduce it. The
> userfaultfd self test turns out to reproduce it reliably, so the
> thinking up to this point was that it just happened to reproduce some
> non-userfaultfd-specific issue. But from Mike's description, it seems
> this bug is very specific to userfaultfd after all. :)
>
That's fine, I'll take an initial look at least. If I end up being
roped into userfaultfd stuff way over my head I'll solicit your help
or punt it over to you.Thanks!
next prev parent reply other threads:[~2021-05-11 7:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 21:21 resv_huge_page underflow with userfaultfd test Mina Almasry
2021-05-11 0:33 ` Mike Kravetz
2021-05-11 0:52 ` Mina Almasry
2021-05-11 6:45 ` Axel Rasmussen
2021-05-11 7:08 ` Mina Almasry [this message]
2021-05-11 16:38 ` Mike Kravetz
2021-05-11 19:08 ` Mina Almasry
2021-05-12 2:25 ` Mike Kravetz
2021-05-12 2:35 ` Peter Xu
2021-05-12 3:06 ` 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=CAHS8izPvx0WzK5C+NWvWPRqvb1OWABv8_FvOcDS+L+5gvz6D2Q@mail.gmail.com \
--to=almasrymina@google.com \
--cc=aarcange@redhat.com \
--cc=axelrasmussen@google.com \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.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;
as well as URLs for NNTP newsgroup(s).