From patchwork Fri Jan 29 06:27:47 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ruan Shiyang X-Patchwork-Id: 12055283 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A6BF2C43381 for ; Fri, 29 Jan 2021 06:29:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7148864DFB for ; Fri, 29 Jan 2021 06:29:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232170AbhA2G3Z (ORCPT ); Fri, 29 Jan 2021 01:29:25 -0500 Received: from mail.cn.fujitsu.com ([183.91.158.132]:4889 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S232155AbhA2G3S (ORCPT ); Fri, 29 Jan 2021 01:29:18 -0500 X-IronPort-AV: E=Sophos;i="5.79,384,1602518400"; d="scan'208";a="103973619" Received: from unknown (HELO cn.fujitsu.com) ([10.167.33.5]) by heian.cn.fujitsu.com with ESMTP; 29 Jan 2021 14:28:05 +0800 Received: from G08CNEXMBPEKD04.g08.fujitsu.local (unknown [10.167.33.201]) by cn.fujitsu.com (Postfix) with ESMTP id 304B448990D2; Fri, 29 Jan 2021 14:28:01 +0800 (CST) Received: from G08CNEXCHPEKD04.g08.fujitsu.local (10.167.33.200) by G08CNEXMBPEKD04.g08.fujitsu.local (10.167.33.201) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 29 Jan 2021 14:28:01 +0800 Received: from irides.mr.mr.mr (10.167.225.141) by G08CNEXCHPEKD04.g08.fujitsu.local (10.167.33.209) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Fri, 29 Jan 2021 14:28:01 +0800 From: Shiyang Ruan To: , , , , , CC: , , , , , , , , Subject: [PATCH RESEND v2 00/10] fsdax: introduce fs query to support reflink Date: Fri, 29 Jan 2021 14:27:47 +0800 Message-ID: <20210129062757.1594130-1-ruansy.fnst@cn.fujitsu.com> X-Mailer: git-send-email 2.30.0 MIME-Version: 1.0 X-yoursite-MailScanner-ID: 304B448990D2.AA014 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: ruansy.fnst@cn.fujitsu.com Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org This patchset is aimed to support shared pages tracking for fsdax. Resend V2: - Cc dm-devel instead of linux-raid Change from V1: - Add the old memory-failure handler back for rolling back - Add callback in MD's ->rmap() to support multiple mapping of dm device - Add judgement for CONFIG_SYSFS - Add pfn_valid() judgement in hwpoison_filter() - Rebased to v5.11-rc5 Change from RFC v3: - Do not lock dax entry in memory failure handler - Add a helper function for corrupted_range - Add restrictions in xfs code - Fix code style - remove the useless association and lock in fsdax Change from RFC v2: - Adjust the order of patches - Divide the infrastructure and the drivers that use it - Rebased to v5.10 Change from RFC v1: - Introduce ->block_lost() for block device - Support mapped device - Add 'not available' warning for realtime device in XFS - Rebased to v5.10-rc1 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 pmem device calls its ->corrupted_range() to find the filesystem which the corrupted data located in, and call filesystem handler to track files or metadata assocaited 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() gendisk->fops->corrupted_range() => - pmem_corrupted_range() - md_blk_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_mapping_kill_procs() The fsdax & reflink support for XFS is not contained in this patchset. (Rebased on v5.11-rc5) Shiyang Ruan (10): pagemap: Introduce ->memory_failure() blk: Introduce ->corrupted_range() for block device fs: Introduce ->corrupted_range() for superblock mm, fsdax: Refactor memory-failure handler for dax mapping mm, pmem: Implement ->memory_failure() in pmem driver pmem: Implement ->corrupted_range() for pmem driver dm: Introduce ->rmap() to find bdev offset md: Implement ->corrupted_range() xfs: Implement ->corrupted_range() for XFS fs/dax: Remove useless functions block/genhd.c | 6 ++ drivers/md/dm-linear.c | 20 ++++ drivers/md/dm.c | 61 +++++++++++ drivers/nvdimm/pmem.c | 44 ++++++++ fs/block_dev.c | 42 +++++++- fs/dax.c | 63 ++++------- fs/xfs/xfs_fsops.c | 5 + fs/xfs/xfs_mount.h | 1 + fs/xfs/xfs_super.c | 109 +++++++++++++++++++ include/linux/blkdev.h | 2 + include/linux/dax.h | 1 + include/linux/device-mapper.h | 5 + include/linux/fs.h | 2 + include/linux/genhd.h | 3 + include/linux/memremap.h | 8 ++ include/linux/mm.h | 9 ++ mm/memory-failure.c | 190 +++++++++++++++++++++++----------- 17 files changed, 466 insertions(+), 105 deletions(-)