From: Andrew Morton <akpm@linux-foundation.org>
To: Jiaqi Yan <jiaqiyan@google.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"shy828301@gmail.com" <shy828301@gmail.com>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"kirill@shutemov.name" <kirill@shutemov.name>,
"tongtiangen@huawei.com" <tongtiangen@huawei.com>,
"naoya.horiguchi@nec.com" <naoya.horiguchi@nec.com>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"osalvador@suse.de" <osalvador@suse.de>
Subject: Re: [PATCH v7 1/2] mm/khugepaged: recover from poisoned anonymous memory
Date: Fri, 18 Nov 2022 14:18:04 -0800 [thread overview]
Message-ID: <20221118141804.c77bdba99f82c38c667edef0@linux-foundation.org> (raw)
In-Reply-To: <CACw3F50i8YMntsOpimZZwthE3F6Ft1uhT-2ybXOfA+p2k0wPhQ@mail.gmail.com>
On Fri, 18 Nov 2022 11:38:22 -0800 Jiaqi Yan <jiaqiyan@google.com> wrote:
> > I had copied this function from an earlier version of your patch, but
> > there was a suggestion that copy_mc_user_highpage() would be a
> > more consistent name with other copy code that can handle machine
> > checks. There was also an upstream change to copy_highpage()
> > that needed to be reflected here.
>
> Thanks for pointing this out, Tony. Is it the kmsan_copy_page_meta(to,
> from) call in copy_highpage()? I will make sure to include it in
> copy_highpage_mc(). If there is more, can you provide lore pointers?
>
Please prepare this series against the mm-unstable branch of
//git.kernel.org/pub/scm/linux/kernel/git/akpm/mm. That way you'll
pick up Tony's change and anything else which might affect this work.
next prev parent reply other threads:[~2022-11-18 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 1:31 [PATCH v7 0/2] Memory poison recovery in khugepaged collapsing Jiaqi Yan
2022-11-18 1:31 ` [PATCH v7 1/2] mm/khugepaged: recover from poisoned anonymous memory Jiaqi Yan
2022-11-18 16:46 ` Luck, Tony
2022-11-18 19:38 ` Jiaqi Yan
2022-11-18 22:18 ` Andrew Morton [this message]
2022-11-18 1:31 ` [PATCH v7 2/2] mm/khugepaged: recover from poisoned file-backed memory Jiaqi Yan
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=20221118141804.c77bdba99f82c38c667edef0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jiaqiyan@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=tongtiangen@huawei.com \
--cc=tony.luck@intel.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