linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: Hugh Dickins <hughd@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Nadav Amit <nadav.amit@gmail.com>
Subject: Re: [PATCH] mm/khugepaged: Detecting uffd-wp vma more efficiently
Date: Thu, 23 Sep 2021 13:53:28 -0400	[thread overview]
Message-ID: <YUy/GKdVvB16ePF/@t490s> (raw)
In-Reply-To: <CAJHvVcg=oQBcuFjT_RO-_0VMtmyTzkzmUaUv0-zX42CnRWbBAg@mail.gmail.com>

On Thu, Sep 23, 2021 at 09:47:42AM -0700, Axel Rasmussen wrote:
> My thinking there was a THP collapse bug was really just based on
> speculation, not a real reproducer, so it's very possible my
> speculation was wrong. It will take some more thinking and reading to
> convince myself one way or the other. :) Thanks to you and Hugh for
> all the details.
> 
> I'd prefer not to add this fix "just in case", if it isn't a real
> problem, as it seems like it may confuse future readers of the code.

It's not "just in case" to me - IMHO it's theoretically causing more false
positives as I used to mention, at least that's my understanding so far. So if
the theory is correct it'll 100% happen when khugepaged merged some
minor-registered regions.

Uffd-wp could have many false positives like this if we don't support swap - at
last we decided to fully support swap then we removed all the false positives
regarding swapping.  I think it's similar here, but khugepaged should trigger
much less frequently on the false positives upon uffd-minor, than swapping upon
uffd-wp.

But yes, there's definitely no rush on thinking or anything - it'll never hurt
to think more. And more importantly, verify it with some test program would be
great; after all theoretically it'll just work like a charm to me.

> 
> I'll send out a patch for it if / when I manage to build a real
> reproducer. Or, in the meantime, some of my Google colleagues are
> testing this code via their live migration implementation, so if there
> is a bug here there's a good chance we'll find it that way too.

Sounds like a good plan.

Thanks,

-- 
Peter Xu


      reply	other threads:[~2021-09-23 17:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 17:51 [PATCH] mm/khugepaged: Detecting uffd-wp vma more efficiently Peter Xu
2021-09-22 18:21 ` David Hildenbrand
2021-09-22 18:58   ` Peter Xu
2021-09-22 19:29     ` Yang Shi
2021-09-22 20:04       ` Peter Xu
2021-09-22 20:23         ` Peter Xu
2021-09-24 10:05     ` David Hildenbrand
2021-09-22 19:33 ` Peter Xu
2021-09-22 20:49 ` Axel Rasmussen
2021-09-22 21:20   ` Peter Xu
2021-09-22 23:18     ` Hugh Dickins
2021-09-22 23:44       ` Peter Xu
2021-09-23  1:22         ` Hugh Dickins
2021-09-23  2:18           ` Peter Xu
2021-09-23 16:47             ` Axel Rasmussen
2021-09-23 17:53               ` Peter Xu [this message]

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=YUy/GKdVvB16ePF/@t490s \
    --to=peterx@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nadav.amit@gmail.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).