From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, songmuchun@bytedance.com,
joao.m.martins@oracle.com, akpm@linux-foundation.org
Subject: [folded-merged] mm-hugetlb_vmemmap-remap-head-page-to-newly-allocated-page-v4.patch removed from -mm tree
Date: Wed, 30 Nov 2022 15:44:38 -0800 [thread overview]
Message-ID: <20221130234438.DF99CC433D7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-hugetlb_vmemmap-remap-head-page-to-newly-allocated-page-v4
has been removed from the -mm tree. Its filename was
mm-hugetlb_vmemmap-remap-head-page-to-newly-allocated-page-v4.patch
This patch was dropped because it was folded into mm-hugetlb_vmemmap-remap-head-page-to-newly-allocated-page.patch
------------------------------------------------------
From: Joao Martins <joao.m.martins@oracle.com>
Subject: mm-hugetlb_vmemmap-remap-head-page-to-newly-allocated-page-v4
Date: Thu, 10 Nov 2022 12:12:14 +0000
add smp_wmb() to ensure page contents are visible prior to PTE write
Link: https://lkml.kernel.org/r/20221110121214.6297-1-joao.m.martins@oracle.com
Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
Reviewed-by: Muchun Song <songmuchun@bytedance.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/hugetlb_vmemmap.c | 7 +++++++
1 file changed, 7 insertions(+)
--- a/mm/hugetlb_vmemmap.c~mm-hugetlb_vmemmap-remap-head-page-to-newly-allocated-page-v4
+++ a/mm/hugetlb_vmemmap.c
@@ -246,6 +246,13 @@ static void vmemmap_remap_pte(pte_t *pte
if (unlikely(addr == walk->reuse_addr)) {
pgprot = PAGE_KERNEL;
list_del(&walk->reuse_page->lru);
+
+ /*
+ * Makes sure that preceding stores to the page contents from
+ * vmemmap_remap_free() become visible before the set_pte_at()
+ * write.
+ */
+ smp_wmb();
}
entry = mk_pte(walk->reuse_page, pgprot);
_
Patches currently in -mm which might be from joao.m.martins@oracle.com are
mm-hugetlb_vmemmap-remap-head-page-to-newly-allocated-page.patch
reply other threads:[~2022-11-30 23:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221130234438.DF99CC433D7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=joao.m.martins@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=songmuchun@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.