From patchwork Tue Dec 15 12:14:05 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ruan Shiyang X-Patchwork-Id: 11974653 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=ham 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 2D4C8C2BB9A for ; Tue, 15 Dec 2020 12:14:35 +0000 (UTC) Received: from ml01.01.org (ml01.01.org [198.145.21.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A50E222241 for ; Tue, 15 Dec 2020 12:14:34 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A50E222241 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=cn.fujitsu.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvdimm-bounces@lists.01.org Received: from ml01.vlan13.01.org (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id 51E9B100EBBC0; Tue, 15 Dec 2020 04:14:34 -0800 (PST) Received-SPF: None (mailfrom) identity=mailfrom; client-ip=183.91.158.132; helo=heian.cn.fujitsu.com; envelope-from=ruansy.fnst@cn.fujitsu.com; receiver= Received: from heian.cn.fujitsu.com (mail.cn.fujitsu.com [183.91.158.132]) by ml01.01.org (Postfix) with ESMTP id 7399D100EBBA8 for ; Tue, 15 Dec 2020 04:14:31 -0800 (PST) X-IronPort-AV: E=Sophos;i="5.78,420,1599494400"; d="scan'208";a="102420175" Received: from unknown (HELO cn.fujitsu.com) ([10.167.33.5]) by heian.cn.fujitsu.com with ESMTP; 15 Dec 2020 20:14:30 +0800 Received: from G08CNEXMBPEKD05.g08.fujitsu.local (unknown [10.167.33.204]) by cn.fujitsu.com (Postfix) with ESMTP id 649AF4CE5CCA; Tue, 15 Dec 2020 20:14:29 +0800 (CST) Received: from G08CNEXCHPEKD05.g08.fujitsu.local (10.167.33.203) by G08CNEXMBPEKD05.g08.fujitsu.local (10.167.33.204) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 15 Dec 2020 20:14:28 +0800 Received: from localhost.localdomain (10.167.225.141) by G08CNEXCHPEKD05.g08.fujitsu.local (10.167.33.209) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Tue, 15 Dec 2020 20:14:28 +0800 From: Shiyang Ruan To: , , , Subject: [RFC PATCH v3 0/9] fsdax: introduce fs query to support reflink Date: Tue, 15 Dec 2020 20:14:05 +0800 Message-ID: <20201215121414.253660-1-ruansy.fnst@cn.fujitsu.com> X-Mailer: git-send-email 2.29.2 MIME-Version: 1.0 X-yoursite-MailScanner-ID: 649AF4CE5CCA.AE812 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: ruansy.fnst@cn.fujitsu.com Message-ID-Hash: DHM4L2HS2D25424XHYMROA6QN2PPURFX X-Message-ID-Hash: DHM4L2HS2D25424XHYMROA6QN2PPURFX X-MailFrom: ruansy.fnst@cn.fujitsu.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header 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 X-Mailman-Version: 3.1.1 Precedence: list List-Id: "Linux-nvdimm developer list." Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: This patchset is a try to resolve the problem of tracking shared page for fsdax. Change from v2: - Adjust the order of patches - Divide the infrastructure and the drivers that use it - Rebased to v5.10 Change from 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.10) --- Shiyang Ruan (9): 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 block/genhd.c | 12 +++ drivers/md/dm-linear.c | 8 ++ drivers/md/dm.c | 66 +++++++++++++++ drivers/nvdimm/pmem.c | 51 ++++++++++++ fs/block_dev.c | 21 +++++ fs/dax.c | 24 +++--- fs/xfs/xfs_fsops.c | 10 +++ fs/xfs/xfs_mount.h | 2 + fs/xfs/xfs_super.c | 93 +++++++++++++++++++++ include/linux/blkdev.h | 2 + include/linux/dax.h | 5 +- include/linux/device-mapper.h | 2 + include/linux/fs.h | 2 + include/linux/genhd.h | 8 ++ include/linux/memremap.h | 8 ++ include/linux/mm.h | 9 ++ mm/memory-failure.c | 150 +++++++++++++++++++--------------- 17 files changed, 391 insertions(+), 82 deletions(-)