From: David Hildenbrand <david@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Muhammad Usama Anjum <usama.anjum@collabora.com>
Subject: Re: [PATCH] mm/memory: Fix missing pte marker for !page on pte zaps
Date: Wed, 13 Mar 2024 23:29:35 +0100 [thread overview]
Message-ID: <4a1f9359-8ecb-4962-92f5-a52cf2fd8564@redhat.com> (raw)
In-Reply-To: <ZfIoFP4lGXW3el8b@x1n>
On 13.03.24 23:26, Peter Xu wrote:
> On Wed, Mar 13, 2024 at 11:03:04PM +0100, David Hildenbrand wrote:
>> On 13.03.24 22:31, peterx@redhat.com wrote:
>>> From: Peter Xu <peterx@redhat.com>
>>>
>>> Commit 0cf18e839f64 of large folio zap work broke uffd-wp. Now mm's uffd
>>> unit test "wp-unpopulated" will trigger this WARN_ON_ONCE().
>>
>> Good that I added the WARN_ON_ONCE() :)
>
> To be explict, VM_WARN_ON_ONCE. :) And that's my guess that you didn't hit
> it when you posted the series and did the tests, as I know latest distros
> like Fedora dropped DEBUG_VM, so maybe you had your base config out of
> there (but I normally have it irrelevant of that).
It's rather surprising that this went unnoticed for quite a while. I
usually do run with DEBUG_VM, but I have a bunch of different VMs where
I tests stuff, likely it was off when I ran the selftests.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-03-13 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 21:31 peterx
2024-03-13 22:03 ` David Hildenbrand
2024-03-13 22:26 ` David Hildenbrand
2024-03-13 22:26 ` Peter Xu
2024-03-13 22:29 ` David Hildenbrand [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=4a1f9359-8ecb-4962-92f5-a52cf2fd8564@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=usama.anjum@collabora.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