From: Shiyang Ruan <ruansy.fnst@fujitsu.com> To: <linux-kernel@vger.kernel.org>, <linux-xfs@vger.kernel.org>, <linux-nvdimm@lists.01.org>, <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 v4 00/10] fsdax: introduce fs query to support reflink Date: Fri, 4 Jun 2021 09:18:34 +0800 [thread overview] Message-ID: <20210604011844.1756145-1-ruansy.fnst@fujitsu.com> (raw) This patchset is aimed to support shared pages tracking for fsdax. Change from V3: - Introduce dax_device->holder to split dax specific issues from block device, instead of the ->corrupted_range() in block_device_operations - Other mistakes and problems fix - Rebased to v5.13-rc4 This patchset moves owner tracking from dax_assocaite_entry() to pmem device driver, by introducing an interface ->memory_failure() of 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() pgmap->ops->memory_failure() => pmem_pgmap_memory_failure() dax_device->holder_ops->corrupted_range() => - fs_dax_corrupted_range() - md_dax_corrupted_range() sb->s_ops->currupted_range() => xfs_fs_corrupted_range() xfs_rmap_query_range() xfs_currupt_helper() * corrupted on metadata try to recover data, call xfs_force_shutdown() * corrupted on file data try to recover data, call mf_dax_kill_procs() The fsdax & reflink support for XFS is not contained in this patchset. (Rebased on v5.13-rc4) == Shiyang Ruan (10): pagemap: Introduce ->memory_failure() dax: Introduce holder for dax_device fs: Introduce ->corrupted_range() for superblock mm, fsdax: Refactor memory-failure handler for dax mapping mm, pmem: Implement ->memory_failure() in pmem driver fs/dax: Implement dax_holder_operations dm: Introduce ->rmap() to find bdev offset md: Implement dax_holder_operations xfs: Implement ->corrupted_range() for XFS fs/dax: Remove useless functions block/genhd.c | 30 ++++++ drivers/dax/super.c | 38 ++++++++ drivers/md/dm-linear.c | 20 ++++ drivers/md/dm.c | 119 ++++++++++++++++++++++- drivers/nvdimm/pmem.c | 14 +++ fs/dax.c | 79 +++++++--------- fs/xfs/xfs_fsops.c | 5 + fs/xfs/xfs_mount.h | 1 + fs/xfs/xfs_super.c | 108 +++++++++++++++++++++ include/linux/dax.h | 13 +++ include/linux/device-mapper.h | 5 + include/linux/fs.h | 2 + include/linux/genhd.h | 1 + include/linux/memremap.h | 8 ++ include/linux/mm.h | 9 ++ mm/memory-failure.c | 173 ++++++++++++++++++++++------------ 16 files changed, 520 insertions(+), 105 deletions(-) -- 2.31.1
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>, <linux-nvdimm@lists.01.org>, <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 v4 00/10] fsdax: introduce fs query to support reflink Date: Fri, 4 Jun 2021 09:18:34 +0800 [thread overview] Message-ID: <20210604011844.1756145-1-ruansy.fnst@fujitsu.com> (raw) This patchset is aimed to support shared pages tracking for fsdax. Change from V3: - Introduce dax_device->holder to split dax specific issues from block device, instead of the ->corrupted_range() in block_device_operations - Other mistakes and problems fix - Rebased to v5.13-rc4 This patchset moves owner tracking from dax_assocaite_entry() to pmem device driver, by introducing an interface ->memory_failure() of 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() pgmap->ops->memory_failure() => pmem_pgmap_memory_failure() dax_device->holder_ops->corrupted_range() => - fs_dax_corrupted_range() - md_dax_corrupted_range() sb->s_ops->currupted_range() => xfs_fs_corrupted_range() xfs_rmap_query_range() xfs_currupt_helper() * corrupted on metadata try to recover data, call xfs_force_shutdown() * corrupted on file data try to recover data, call mf_dax_kill_procs() The fsdax & reflink support for XFS is not contained in this patchset. (Rebased on v5.13-rc4) == Shiyang Ruan (10): pagemap: Introduce ->memory_failure() dax: Introduce holder for dax_device fs: Introduce ->corrupted_range() for superblock mm, fsdax: Refactor memory-failure handler for dax mapping mm, pmem: Implement ->memory_failure() in pmem driver fs/dax: Implement dax_holder_operations dm: Introduce ->rmap() to find bdev offset md: Implement dax_holder_operations xfs: Implement ->corrupted_range() for XFS fs/dax: Remove useless functions block/genhd.c | 30 ++++++ drivers/dax/super.c | 38 ++++++++ drivers/md/dm-linear.c | 20 ++++ drivers/md/dm.c | 119 ++++++++++++++++++++++- drivers/nvdimm/pmem.c | 14 +++ fs/dax.c | 79 +++++++--------- fs/xfs/xfs_fsops.c | 5 + fs/xfs/xfs_mount.h | 1 + fs/xfs/xfs_super.c | 108 +++++++++++++++++++++ include/linux/dax.h | 13 +++ include/linux/device-mapper.h | 5 + include/linux/fs.h | 2 + include/linux/genhd.h | 1 + include/linux/memremap.h | 8 ++ include/linux/mm.h | 9 ++ mm/memory-failure.c | 173 ++++++++++++++++++++++------------ 16 files changed, 520 insertions(+), 105 deletions(-) -- 2.31.1 -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel
next reply other threads:[~2021-06-04 1:19 UTC|newest] Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-04 1:18 Shiyang Ruan [this message] 2021-06-04 1:18 ` [dm-devel] [PATCH v4 00/10] fsdax: introduce fs query to support reflink Shiyang Ruan 2021-06-04 1:18 ` [PATCH v4 01/10] pagemap: Introduce ->memory_failure() Shiyang Ruan 2021-06-04 1:18 ` [dm-devel] " Shiyang Ruan 2021-06-16 0:18 ` Dan Williams 2021-06-16 0:18 ` Dan Williams 2021-06-04 1:18 ` [PATCH v4 02/10] dax: Introduce holder for dax_device Shiyang Ruan 2021-06-04 1:18 ` [dm-devel] " Shiyang Ruan 2021-06-16 0:46 ` Dan Williams 2021-06-16 0:46 ` Dan Williams 2021-06-04 1:18 ` [PATCH v4 03/10] fs: Introduce ->corrupted_range() for superblock Shiyang Ruan 2021-06-04 1:18 ` [dm-devel] " Shiyang Ruan 2021-06-16 0:48 ` Dan Williams 2021-06-16 0:48 ` Dan Williams 2021-06-17 6:51 ` ruansy.fnst 2021-06-17 6:51 ` [dm-devel] " ruansy.fnst 2021-06-17 7:04 ` Dan Williams 2021-06-17 7:04 ` Dan Williams 2021-06-17 8:12 ` ruansy.fnst 2021-06-17 8:12 ` [dm-devel] " ruansy.fnst 2021-06-04 1:18 ` [PATCH v4 04/10] mm, fsdax: Refactor memory-failure handler for dax mapping Shiyang Ruan 2021-06-04 1:18 ` [dm-devel] " Shiyang Ruan 2021-06-16 6:30 ` Dan Williams 2021-06-16 6:30 ` Dan Williams 2021-06-17 7:51 ` ruansy.fnst 2021-06-17 7:51 ` [dm-devel] " ruansy.fnst 2021-06-04 1:18 ` [PATCH v4 05/10] mm, pmem: Implement ->memory_failure() in pmem driver Shiyang Ruan 2021-06-04 1:18 ` [dm-devel] " Shiyang Ruan 2021-06-16 6:49 ` Dan Williams 2021-06-16 6:49 ` Dan Williams 2021-06-04 1:18 ` [PATCH v4 06/10] fs/dax: Implement dax_holder_operations Shiyang Ruan 2021-06-04 1:18 ` [dm-devel] " Shiyang Ruan 2021-06-04 1:18 ` [PATCH v4 07/10] dm: Introduce ->rmap() to find bdev offset Shiyang Ruan 2021-06-04 1:18 ` [dm-devel] " Shiyang Ruan 2021-06-04 1:18 ` [PATCH v4 08/10] md: Implement dax_holder_operations Shiyang Ruan 2021-06-04 1:18 ` [dm-devel] " Shiyang Ruan 2021-06-04 5:48 ` kernel test robot 2021-06-04 5:48 ` kernel test robot 2021-06-04 5:48 ` kernel test robot 2021-06-04 1:18 ` [PATCH v4 09/10] xfs: Implement ->corrupted_range() for XFS Shiyang Ruan 2021-06-04 1:18 ` [dm-devel] " Shiyang Ruan 2021-06-04 5:22 ` kernel test robot 2021-06-04 5:22 ` kernel test robot 2021-06-04 5:22 ` [dm-devel] " kernel test robot 2021-06-04 5:40 ` kernel test robot 2021-06-04 5:40 ` kernel test robot 2021-06-04 5:40 ` kernel test robot 2021-06-04 1:18 ` [PATCH v4 10/10] fs/dax: Remove useless functions Shiyang Ruan 2021-06-04 1:18 ` [dm-devel] " 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=20210604011844.1756145-1-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-nvdimm@lists.01.org \ --cc=linux-xfs@vger.kernel.org \ --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.