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: <darrick.wong@oracle.com>, <dan.j.williams@intel.com>, <david@fromorbit.com>, <hch@lst.de>, <agk@redhat.com>, <snitzer@redhat.com>, <rgoldwyn@suse.de> Subject: [PATCH v5 1/9] pagemap: Introduce ->memory_failure() Date: Mon, 28 Jun 2021 08:02:10 +0800 [thread overview] Message-ID: <20210628000218.387833-2-ruansy.fnst@fujitsu.com> (raw) In-Reply-To: <20210628000218.387833-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 45a79da89c5f..d96da47cc249 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
WARNING: multiple messages have this Message-ID (diff)
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: snitzer@redhat.com, darrick.wong@oracle.com, rgoldwyn@suse.de, david@fromorbit.com, dan.j.williams@intel.com, hch@lst.de, agk@redhat.com Subject: [dm-devel] [PATCH v5 1/9] pagemap: Introduce ->memory_failure() Date: Mon, 28 Jun 2021 08:02:10 +0800 [thread overview] Message-ID: <20210628000218.387833-2-ruansy.fnst@fujitsu.com> (raw) In-Reply-To: <20210628000218.387833-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 45a79da89c5f..d96da47cc249 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 -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-06-28 0:03 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-28 0:02 [PATCH v5 0/9] fsdax: introduce fs query to support reflink Shiyang Ruan 2021-06-28 0:02 ` [dm-devel] " Shiyang Ruan 2021-06-28 0:02 ` Shiyang Ruan [this message] 2021-06-28 0:02 ` [dm-devel] [PATCH v5 1/9] pagemap: Introduce ->memory_failure() Shiyang Ruan 2021-06-28 0:02 ` [PATCH v5 2/9] dax: Introduce holder for dax_device Shiyang Ruan 2021-06-28 0:02 ` [dm-devel] " Shiyang Ruan 2021-07-19 15:17 ` Christoph Hellwig 2021-07-19 15:17 ` [dm-devel] " Christoph Hellwig 2021-07-20 10:37 ` ruansy.fnst 2021-07-20 10:37 ` [dm-devel] " ruansy.fnst 2021-06-28 0:02 ` [PATCH v5 3/9] mm: factor helpers for memory_failure_dev_pagemap Shiyang Ruan 2021-06-28 0:02 ` [dm-devel] " Shiyang Ruan 2021-06-28 0:02 ` [PATCH v5 4/9] pmem,mm: Implement ->memory_failure in pmem driver Shiyang Ruan 2021-06-28 0:02 ` [dm-devel] [PATCH v5 4/9] pmem, mm: " Shiyang Ruan 2021-06-28 0:02 ` [PATCH v5 5/9] mm: Introduce mf_dax_kill_procs() for fsdax case Shiyang Ruan 2021-06-28 0:02 ` [dm-devel] " Shiyang Ruan 2021-06-28 3:23 ` kernel test robot 2021-06-28 3:23 ` kernel test robot 2021-06-28 3:23 ` [dm-devel] " kernel test robot 2021-06-28 11:49 ` Matthew Wilcox 2021-06-28 11:49 ` [dm-devel] " Matthew Wilcox 2021-06-29 7:49 ` ruansy.fnst 2021-06-29 7:49 ` [dm-devel] " ruansy.fnst 2021-06-29 11:46 ` Matthew Wilcox 2021-06-29 11:46 ` [dm-devel] " Matthew Wilcox 2021-07-16 6:32 ` ruansy.fnst 2021-07-16 6:32 ` [dm-devel] " ruansy.fnst 2021-06-28 0:02 ` [PATCH v5 6/9] xfs: Implement ->corrupted_range() for XFS Shiyang Ruan 2021-06-28 0:02 ` [dm-devel] " Shiyang Ruan 2021-06-28 2:02 ` kernel test robot 2021-06-28 2:02 ` kernel test robot 2021-06-28 2:02 ` [dm-devel] " kernel test robot 2021-06-28 3:05 ` kernel test robot 2021-06-28 3:05 ` kernel test robot 2021-06-28 3:05 ` [dm-devel] " kernel test robot 2021-06-28 0:02 ` [PATCH v5 7/9] dm: Introduce ->rmap() to find bdev offset Shiyang Ruan 2021-06-28 0:02 ` [dm-devel] " Shiyang Ruan 2021-06-28 0:02 ` [PATCH v5 8/9] md: Implement dax_holder_operations Shiyang Ruan 2021-06-28 0:02 ` [dm-devel] " Shiyang Ruan 2021-06-28 0:02 ` [PATCH v5 9/9] fs/dax: Remove useless functions Shiyang Ruan 2021-06-28 0:02 ` [dm-devel] " Shiyang Ruan 2021-07-19 15:18 ` Christoph Hellwig 2021-07-19 15:18 ` [dm-devel] " Christoph Hellwig
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=20210628000218.387833-2-ruansy.fnst@fujitsu.com \ --to=ruansy.fnst@fujitsu.com \ --cc=agk@redhat.com \ --cc=dan.j.williams@intel.com \ --cc=darrick.wong@oracle.com \ --cc=david@fromorbit.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=rgoldwyn@suse.de \ --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: linkBe 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.