From: Asahi Lina <lina@asahilina.net>
To: Alistair Popple <apopple@nvidia.com>,
David Hildenbrand <david@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Sergio Lopez Pascual <slp@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
asahi@lists.linux.dev, Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] mm: Fix __wp_page_copy_user fallback path for remote mm
Date: Tue, 12 Nov 2024 18:48:33 +0900 [thread overview]
Message-ID: <821d15f9-233e-4b9d-8194-5de1835113c7@asahilina.net> (raw)
In-Reply-To: <87ttceu0i8.fsf@nvdebian.thelocal>
On 11/11/24 8:24 AM, Alistair Popple wrote:
>
> David Hildenbrand <david@redhat.com> writes:
>
>> On 07.11.24 18:32, Asahi Lina wrote:
>>> On 11/8/24 2:14 AM, David Hildenbrand wrote:
>>>> I recall that there is still a problem with false-positives on
>>>> folio_test_anon() with ZONE_DEVICE pages, so it's maybe not that
>>>> easy ... and the whole get_dev_pagemap() stuff is nasty.
>
> Specifically FS DAX reuses PAGE_MAPPING_ANON in
> include/linux/page-flags.h
>
> /*
> * Different with flags above, this flag is used only for fsdax mode. It
> * indicates that this page->mapping is now under reflink case.
> */
> #define PAGE_MAPPING_DAX_SHARED ((void *)0x1)
>
> FS DAX pages are never anon though, so you could probably test for
> !vma_is_dax() and/or add an implementation of is_fsdax_page().
>
>>>> Likely we would have to do what GUP does, and temporarily grab a pgmap
>>>> reference. Gah.
>>>>
>>>>
>>>> So if we sort out the pagemap stuff and the possibly wrong
>>>> folio_test_anon() on some ZONE_DEVICE pages (but not all, because IIRC
>>>> DEVICE_PRIVATE can be anon ...), it might be doable.
>
> Correct, DEVICE_PRIVATE and DEVICE_COHERENT pages are always anon (at
> least for now).
>
>>>> But it sounds ugly, especially because that code might change soon and
>>>> not require messing with ZONE_DEVICE pages on that level.
>
> Yes, I'm hopoing to get the next version of that series posted this
> week. I found a couple of other FS DAX bugs that slowed me down.
>
> - Alistair
>
>>>> And then, we'd not be able to handle VM_PFNMAP cleanly ...
>>>>
If this is all going to be fixed another way soon then I think there's
no rush to get a workaround in earlier than that, I just don't want it
to fall by the wayside.
We have my original patch downstream in libkrunfw (which despite the
lockdep complaints does work in practice), so we can keep that in until
the proper solution lands upstream.
Alistair, can you Cc me on future submissions? So I'm reminded to test
this out (FWIW the case I'm interested in is just `gdb /bin/foo` with
the whole root filesystem on DAX, though I imagine a statically linked
foo on a DAX mount by itself is probably an equivalent repro).
~~ Lina
next prev parent reply other threads:[~2024-11-12 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 12:08 Asahi Lina
2024-11-01 19:07 ` Andrew Morton
2024-11-01 21:18 ` Asahi Lina
2024-11-05 3:42 ` Andrew Morton
2024-11-05 12:03 ` David Hildenbrand
2024-11-07 16:43 ` Asahi Lina
2024-11-07 17:14 ` David Hildenbrand
2024-11-07 17:32 ` Asahi Lina
2024-11-08 9:55 ` David Hildenbrand
2024-11-10 23:24 ` Alistair Popple
2024-11-12 9:48 ` Asahi Lina [this message]
2024-11-12 10:00 ` David Hildenbrand
2024-11-12 11:28 ` Asahi Lina
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=821d15f9-233e-4b9d-8194-5de1835113c7@asahilina.net \
--to=lina@asahilina.net \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=asahi@lists.linux.dev \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=slp@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