From: Shiyang Ruan <ruansy.fnst@fujitsu.com>
To: <linux-kernel@vger.kernel.org>, <linux-xfs@vger.kernel.org>,
<nvdimm@lists.linux.dev>, <linux-mm@kvack.org>,
<linux-fsdevel@vger.kernel.org>
Cc: <djwong@kernel.org>, <dan.j.williams@intel.com>,
<david@fromorbit.com>, <hch@infradead.org>, <jane.chu@oracle.com>
Subject: [PATCH v8 0/8] fsdax: introduce fs query to support reflink
Date: Sun, 31 Oct 2021 23:20:20 +0800 [thread overview]
Message-ID: <20211031152028.3724121-1-ruansy.fnst@fujitsu.com> (raw)
This patchset is aimed to support shared pages tracking for fsdax.
Changes from V7:
- Change dax lock from global rwsem to per-device percpu_rwsem
- Change type of range length from size_t to u64
- Rename 'flags' to 'mf_flags'
- Fix mistakes in XFS code
- Add cow branch for dax_assocaite_entry()
- Rebased to v5.15-rc7
This patchset moves owner tracking from dax_assocaite_entry() to pmem
device driver, by introducing an interface ->memory_failure() for struct
pagemap. This interface is called by memory_failure() in mm, and
implemented by pmem device.
Then call holder operations to find the filesystem which the corrupted
data located in, and call filesystem handler to track files or metadata
associated with this page.
Finally we are able to try to fix the corrupted data in filesystem and
do other necessary processing, such as killing processes who are using
the files affected.
The call trace is like this:
memory_failure()
|* fsdax case
|------------
|pgmap->ops->memory_failure() => pmem_pgmap_memory_failure()
| dax_holder_notify_failure() =>
| dax_device->holder_ops->notify_failure() =>
| - xfs_dax_notify_failure()
| |* xfs_dax_notify_failure()
| |--------------------------
| | xfs_rmap_query_range()
| | xfs_dax_notify_failure_fn()
| | * corrupted on metadata
| | try to recover data, call xfs_force_shutdown()
| | * corrupted on file data
| | try to recover data, call mf_dax_kill_procs()
|* normal case
|-------------
mf_generic_kill_procs()
The fsdax & reflink support for XFS is not contained in this patchset.
(Rebased on v5.15-rc7)
==
Shiyang Ruan (8):
dax: Use rwsem for dax_{read,write}_lock()
dax: Introduce holder for dax_device
mm: factor helpers for memory_failure_dev_pagemap
pagemap,pmem: Introduce ->memory_failure()
fsdax: Introduce dax_lock_mapping_entry()
mm: Introduce mf_dax_kill_procs() for fsdax case
xfs: Implement ->notify_failure() for XFS
fsdax: add exception for reflinked files
drivers/dax/device.c | 11 +-
drivers/dax/super.c | 131 +++++++++++++++++----
drivers/md/dm-writecache.c | 7 +-
drivers/nvdimm/pmem.c | 11 ++
fs/dax.c | 140 +++++++++++++++++------
fs/xfs/xfs_fsops.c | 3 +
fs/xfs/xfs_mount.h | 1 +
fs/xfs/xfs_super.c | 207 +++++++++++++++++++++++++++++++++
include/linux/dax.h | 76 ++++++++++++-
include/linux/memremap.h | 9 ++
include/linux/mm.h | 2 +
mm/memory-failure.c | 226 ++++++++++++++++++++++++++-----------
12 files changed, 687 insertions(+), 137 deletions(-)
--
2.33.0
next reply other threads:[~2021-10-31 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 15:20 Shiyang Ruan [this message]
2021-10-31 15:20 ` [PATCH v8 1/8] dax: Use percpu rwsem for dax_{read,write}_lock() Shiyang Ruan
2021-10-31 17:50 ` kernel test robot
2021-10-31 18:16 ` kernel test robot
2021-10-31 15:20 ` [PATCH v8 2/8] dax: Introduce holder for dax_device Shiyang Ruan
2021-10-31 15:20 ` [PATCH v8 3/8] mm: factor helpers for memory_failure_dev_pagemap Shiyang Ruan
2021-10-31 15:20 ` [PATCH v8 4/8] pagemap,pmem: Introduce ->memory_failure() Shiyang Ruan
2021-10-31 15:20 ` [PATCH v8 5/8] fsdax: Introduce dax_lock_mapping_entry() Shiyang Ruan
2021-10-31 15:20 ` [PATCH v8 6/8] mm: Introduce mf_dax_kill_procs() for fsdax case Shiyang Ruan
2021-10-31 15:20 ` [PATCH v8 7/8] xfs: Implement ->notify_failure() for XFS Shiyang Ruan
2021-10-31 15:20 ` [PATCH v8 8/8] fsdax: add exception for reflinked files Shiyang Ruan
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=20211031152028.3724121-1-ruansy.fnst@fujitsu.com \
--to=ruansy.fnst@fujitsu.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=jane.chu@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).