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>, <dm-devel@redhat.com>
Cc: <djwong@kernel.com>, <dan.j.williams@intel.com>,
<david@fromorbit.com>, <hch@lst.de>, <agk@redhat.com>,
<snitzer@redhat.com>
Subject: [PATCH v6 1/9] pagemap: Introduce ->memory_failure()
Date: Fri, 30 Jul 2021 16:52:37 +0800 [thread overview]
Message-ID: <20210730085245.3069812-2-ruansy.fnst@fujitsu.com> (raw)
In-Reply-To: <20210730085245.3069812-1-ruansy.fnst@fujitsu.com>
When memory-failure occurs, we call this function which is implemented
by each kind of devices. For the fsdax case, pmem device driver
implements it. Pmem device driver will find out the filesystem in which
the corrupted page located in. And finally call filesystem handler to
deal with this error.
The filesystem will try to recover the corrupted data if necessary.
Signed-off-by: Shiyang Ruan <ruansy.fnst@fujitsu.com>
---
include/linux/memremap.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/include/linux/memremap.h b/include/linux/memremap.h
index c0e9d35889e8..ed6980087db5 100644
--- a/include/linux/memremap.h
+++ b/include/linux/memremap.h
@@ -87,6 +87,15 @@ struct dev_pagemap_ops {
* the page back to a CPU accessible page.
*/
vm_fault_t (*migrate_to_ram)(struct vm_fault *vmf);
+
+ /*
+ * Handle the memory failure happens on a range of pfns. Notify the
+ * processes who are using these pfns, and try to recover the data on
+ * them if necessary. The flag is finally passed to the recover
+ * function through the whole notify routine.
+ */
+ int (*memory_failure)(struct dev_pagemap *pgmap, unsigned long pfn,
+ unsigned long nr_pfns, int flags);
};
#define PGMAP_ALTMAP_VALID (1 << 0)
--
2.32.0
next prev parent reply other threads:[~2021-07-30 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 8:52 [PATCH v6 0/9] fsdax: introduce fs query to support reflink Shiyang Ruan
2021-07-30 8:52 ` Shiyang Ruan [this message]
2021-07-30 8:52 ` [PATCH v6 2/9] dax: Introduce holder for dax_device Shiyang Ruan
2021-07-30 8:52 ` [PATCH v6 3/9] mm: factor helpers for memory_failure_dev_pagemap Shiyang Ruan
2021-07-30 8:52 ` [PATCH v6 4/9] pmem,mm: Implement ->memory_failure in pmem driver Shiyang Ruan
2021-07-30 8:52 ` [PATCH v6 5/9] mm: Introduce mf_dax_kill_procs() for fsdax case Shiyang Ruan
2021-07-30 8:52 ` [PATCH v6 6/9] xfs: Implement ->corrupted_range() for XFS Shiyang Ruan
2021-07-30 9:15 ` David Hildenbrand
2021-07-30 9:25 ` ruansy.fnst
2021-07-30 8:52 ` [PATCH v6 7/9] dm: Introduce ->rmap() to find bdev offset Shiyang Ruan
2021-07-30 8:52 ` [PATCH v6 8/9] md: Implement dax_holder_operations Shiyang Ruan
2021-07-30 8:52 ` [PATCH v6 9/9] 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=20210730085245.3069812-2-ruansy.fnst@fujitsu.com \
--to=ruansy.fnst@fujitsu.com \
--cc=agk@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--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 \
--cc=snitzer@redhat.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;
as well as URLs for NNTP newsgroup(s).