From: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com> To: <linux-kernel@vger.kernel.org>, <linux-xfs@vger.kernel.org>, <linux-nvdimm@lists.01.org>, <linux-mm@kvack.org> Cc: linux-fsdevel@vger.kernel.org, linux-raid@vger.kernel.org, darrick.wong@oracle.com, david@fromorbit.com, hch@lst.de, song@kernel.org, rgoldwyn@suse.de, qi.fuli@fujitsu.com, y-goto@fujitsu.com Subject: [PATCH 01/10] pagemap: Introduce ->memory_failure() Date: Thu, 31 Dec 2020 00:55:52 +0800 [thread overview] Message-ID: <20201230165601.845024-2-ruansy.fnst@cn.fujitsu.com> (raw) In-Reply-To: <20201230165601.845024-1-ruansy.fnst@cn.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 block device where the error page locates in, and try to get the filesystem on this block device. And finally call filesystem handler to deal with the error. The filesystem will try to recover the corrupted data if possiable. Signed-off-by: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com> --- include/linux/memremap.h | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/include/linux/memremap.h b/include/linux/memremap.h index 79c49e7f5c30..0bcf2b1e20bd 100644 --- a/include/linux/memremap.h +++ b/include/linux/memremap.h @@ -87,6 +87,14 @@ 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 one page. Notify the processes + * who are using this page, and try to recover the data on this page + * if necessary. + */ + int (*memory_failure)(struct dev_pagemap *pgmap, unsigned long pfn, + int flags); }; #define PGMAP_ALTMAP_VALID (1 << 0) -- 2.29.2 _______________________________________________ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com> To: <linux-kernel@vger.kernel.org>, <linux-xfs@vger.kernel.org>, <linux-nvdimm@lists.01.org>, <linux-mm@kvack.org> Cc: <linux-fsdevel@vger.kernel.org>, <linux-raid@vger.kernel.org>, <darrick.wong@oracle.com>, <dan.j.williams@intel.com>, <david@fromorbit.com>, <hch@lst.de>, <song@kernel.org>, <rgoldwyn@suse.de>, <qi.fuli@fujitsu.com>, <y-goto@fujitsu.com> Subject: [PATCH 01/10] pagemap: Introduce ->memory_failure() Date: Thu, 31 Dec 2020 00:55:52 +0800 [thread overview] Message-ID: <20201230165601.845024-2-ruansy.fnst@cn.fujitsu.com> (raw) In-Reply-To: <20201230165601.845024-1-ruansy.fnst@cn.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 block device where the error page locates in, and try to get the filesystem on this block device. And finally call filesystem handler to deal with the error. The filesystem will try to recover the corrupted data if possiable. Signed-off-by: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com> --- include/linux/memremap.h | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/include/linux/memremap.h b/include/linux/memremap.h index 79c49e7f5c30..0bcf2b1e20bd 100644 --- a/include/linux/memremap.h +++ b/include/linux/memremap.h @@ -87,6 +87,14 @@ 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 one page. Notify the processes + * who are using this page, and try to recover the data on this page + * if necessary. + */ + int (*memory_failure)(struct dev_pagemap *pgmap, unsigned long pfn, + int flags); }; #define PGMAP_ALTMAP_VALID (1 << 0) -- 2.29.2
next prev parent reply other threads:[~2020-12-30 16:58 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-30 16:55 [PATCH 00/10] fsdax: introduce fs query to support reflink Shiyang Ruan 2020-12-30 16:55 ` Shiyang Ruan 2020-12-30 16:55 ` Shiyang Ruan [this message] 2020-12-30 16:55 ` [PATCH 01/10] pagemap: Introduce ->memory_failure() Shiyang Ruan 2020-12-30 16:55 ` [PATCH 02/10] blk: Introduce ->corrupted_range() for block device Shiyang Ruan 2020-12-30 16:55 ` Shiyang Ruan 2021-01-08 9:55 ` Christoph Hellwig 2021-01-08 9:55 ` Christoph Hellwig 2021-01-08 19:09 ` Darrick J. Wong 2021-01-08 19:09 ` Darrick J. Wong 2020-12-30 16:55 ` [PATCH 03/10] fs: Introduce ->corrupted_range() for superblock Shiyang Ruan 2020-12-30 16:55 ` Shiyang Ruan 2021-01-08 9:56 ` Christoph Hellwig 2021-01-08 9:56 ` Christoph Hellwig 2020-12-30 16:55 ` [PATCH 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping Shiyang Ruan 2020-12-30 16:55 ` Shiyang Ruan 2021-01-06 15:41 ` Jan Kara 2021-01-06 15:41 ` Jan Kara 2021-01-12 2:55 ` Ruan Shiyang 2021-01-12 2:55 ` Ruan Shiyang 2021-01-13 10:04 ` zhong jiang 2021-01-13 10:04 ` zhong jiang 2021-01-14 1:44 ` Ruan Shiyang 2021-01-14 1:44 ` Ruan Shiyang 2021-01-14 3:26 ` zhong jiang 2021-01-14 3:26 ` zhong jiang 2021-01-14 3:52 ` Ruan Shiyang 2021-01-14 3:52 ` Ruan Shiyang 2021-01-14 9:38 ` zhong jiang 2021-01-14 9:38 ` zhong jiang 2021-01-14 17:20 ` Darrick J. Wong 2021-01-14 17:20 ` Darrick J. Wong 2021-01-14 20:38 ` Dan Williams 2021-01-14 20:38 ` Dan Williams 2021-01-14 20:38 ` Dan Williams 2020-12-30 16:55 ` [PATCH 05/10] mm, pmem: Implement ->memory_failure() in pmem driver Shiyang Ruan 2020-12-30 16:55 ` Shiyang Ruan 2021-01-06 15:55 ` Jan Kara 2021-01-06 15:55 ` Jan Kara 2020-12-30 16:55 ` [PATCH 06/10] pmem: Implement ->corrupted_range() for " Shiyang Ruan 2020-12-30 16:55 ` Shiyang Ruan 2020-12-30 16:55 ` [PATCH 07/10] dm: Introduce ->rmap() to find bdev offset Shiyang Ruan 2020-12-30 16:55 ` Shiyang Ruan 2020-12-30 16:55 ` [PATCH 08/10] md: Implement ->corrupted_range() Shiyang Ruan 2020-12-30 16:55 ` Shiyang Ruan 2021-01-06 17:14 ` Jan Kara 2021-01-06 17:14 ` Jan Kara 2021-01-12 12:45 ` Ruan Shiyang 2021-01-12 12:45 ` Ruan Shiyang 2020-12-30 16:56 ` [PATCH 09/10] xfs: Implement ->corrupted_range() for XFS Shiyang Ruan 2020-12-30 16:56 ` Shiyang Ruan 2021-01-04 23:21 ` Darrick J. Wong 2021-01-04 23:21 ` Darrick J. Wong 2020-12-30 16:56 ` [PATCH 10/10] fs/dax: remove useless functions Shiyang Ruan 2020-12-30 16:56 ` 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=20201230165601.845024-2-ruansy.fnst@cn.fujitsu.com \ --to=ruansy.fnst@cn.fujitsu.com \ --cc=darrick.wong@oracle.com \ --cc=david@fromorbit.com \ --cc=hch@lst.de \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-nvdimm@lists.01.org \ --cc=linux-raid@vger.kernel.org \ --cc=linux-xfs@vger.kernel.org \ --cc=qi.fuli@fujitsu.com \ --cc=rgoldwyn@suse.de \ --cc=song@kernel.org \ --cc=y-goto@fujitsu.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.