From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
Zi Yan <ziy@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Alistair Popple <apopple@nvidia.com>,
Dan Williams <djbw@kernel.org>
Cc: linux-mm@kvack.org, nvdimm@lists.linux.dev,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mm/huge_memory: take a reference on a folio PUD copied by fork
Date: Fri, 6 Nov 2026 17:32:26 +0100 [thread overview]
Message-ID: <a514a8d4-b9f1-4741-86f2-4671fad24ab8@virtuozzo.com> (raw)
In-Reply-To: <6f035f97-8b55-47ad-bd52-833b86b8ae8f@kernel.org>
On 11/5/26 21:31, David Hildenbrand (Arm) wrote:
> On 11/5/26 21:19, Zi Yan wrote:
...
>> I assume this supersedes David's version[1], which uses
>> folio_add_file_rmap_pud().
>>
>> [1] https://lore.kernel.org/all/20261031-fixes_core-v3-11-d6437171ecc3@kernel.org/
>
> Ugh, I thought I dropped it to wait for this one here. But turns out the flood
> of patches confused me :( (hoping I didn't drop another one by mistake)
>
> It's already part of the fixes PULL request:
>
> https://lore.kernel.org/linux-mm/20261105084704.5703-1-david@kernel.org/
>
> Konstantin, sorry! Can you send a follow up to introduce+use the dup variant?
No problem, will do the follow-up on top of thp-7.5.misc in the mm/core tree.
--
Cheers,
Konstantin.
next prev parent reply other threads:[~2026-11-06 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 17:00 [PATCH v2 0/2] mm/huge_memory: take a reference on a device DAX " Konstantin Khorenko
2026-11-05 17:00 ` [PATCH v2 1/2] mm/huge_memory: take a reference on a folio " Konstantin Khorenko
2026-11-05 19:28 ` David Hildenbrand (Arm)
2026-11-05 20:19 ` Zi Yan
2026-11-05 20:31 ` David Hildenbrand (Arm)
2026-11-06 16:32 ` Konstantin Khorenko [this message]
2026-11-05 17:00 ` [PATCH v2 2/2] selftests/mm: test fork of a device DAX PUD Konstantin Khorenko
2026-11-05 19:30 ` David Hildenbrand (Arm)
2026-11-06 16:26 ` Konstantin Khorenko
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=a514a8d4-b9f1-4741-86f2-4671fad24ab8@virtuozzo.com \
--to=khorenko@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=david@kernel.org \
--cc=djbw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=ziy@nvidia.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
all inboxes | Powered by JetHome®