From: Muchun Song <songmuchun@bytedance.com>
To: dan.j.williams@intel.com, willy@infradead.org, jack@suse.cz,
viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
apopple@nvidia.com, shy828301@gmail.com, rcampbell@nvidia.com,
hughd@google.com, xiyuyang19@fudan.edu.cn,
kirill.shutemov@linux.intel.com, zwisler@kernel.org,
hch@infradead.org
Cc: linux-fsdevel@vger.kernel.org, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
duanxiongchun@bytedance.com,
Muchun Song <songmuchun@bytedance.com>
Subject: [PATCH v2 0/6] Fix some bugs related to ramp and dax
Date: Wed, 2 Feb 2022 22:33:01 +0800 [thread overview]
Message-ID: <20220202143307.96282-1-songmuchun@bytedance.com> (raw)
Patch 1-2 fix a cache flush bug, because subsequent patches depend on
those on those changes, there are placed in this series. Patch 3-4
are preparation for fixing a dax bug in patch 5. Patch 6 is code cleanup
since the previous patch remove the usage of follow_invalidate_pte().
Changes in v2:
- Avoid the overly long line in lots of places suggested by Christoph.
- Fix a compiler warning reported by kernel test robot since pmd_pfn()
is not defined when !CONFIG_TRANSPARENT_HUGEPAGE on powerpc architecture.
- Split a new patch 4 for preparation of fixing the dax bug.
Muchun Song (6):
mm: rmap: fix cache flush on THP pages
dax: fix cache flush on PMD-mapped pages
mm: page_vma_mapped: support checking if a pfn is mapped into a vma
mm: rmap: introduce pfn_mkclean_range() to cleans PTEs
dax: fix missing writeprotect the pte entry
mm: remove range parameter from follow_invalidate_pte()
fs/dax.c | 82 ++++------------------------------------------
include/linux/mm.h | 3 --
include/linux/rmap.h | 17 ++++++++--
include/linux/swapops.h | 13 +++++---
mm/internal.h | 52 +++++++++++++++++++----------
mm/memory.c | 23 ++-----------
mm/page_vma_mapped.c | 68 ++++++++++++++++++++++++--------------
mm/rmap.c | 87 ++++++++++++++++++++++++++++++++++++++-----------
8 files changed, 180 insertions(+), 165 deletions(-)
--
2.11.0
next reply other threads:[~2022-02-02 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 14:33 Muchun Song [this message]
2022-02-02 14:33 ` [PATCH v2 1/6] mm: rmap: fix cache flush on THP pages Muchun Song
2022-02-03 10:16 ` Jan Kara
2022-02-02 14:33 ` [PATCH v2 2/6] dax: fix cache flush on PMD-mapped pages Muchun Song
2022-02-03 10:17 ` Jan Kara
2022-02-02 14:33 ` [PATCH v2 3/6] mm: page_vma_mapped: support checking if a pfn is mapped into a vma Muchun Song
2022-02-02 16:43 ` kernel test robot
2022-02-02 18:28 ` Matthew Wilcox
2022-02-03 0:18 ` kernel test robot
2022-02-03 0:18 ` kernel test robot
2022-02-02 14:33 ` [PATCH v2 4/6] mm: rmap: introduce pfn_mkclean_range() to cleans PTEs Muchun Song
2022-02-02 14:33 ` [PATCH v2 5/6] dax: fix missing writeprotect the pte entry Muchun Song
2022-02-02 14:33 ` [PATCH v2 6/6] mm: remove range parameter from follow_invalidate_pte() Muchun Song
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=20220202143307.96282-1-songmuchun@bytedance.com \
--to=songmuchun@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=duanxiongchun@bytedance.com \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nvdimm@lists.linux.dev \
--cc=rcampbell@nvidia.com \
--cc=shy828301@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=xiyuyang19@fudan.edu.cn \
--cc=zwisler@kernel.org \
/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.