From mboxrd@z Thu Jan 1 00:00:00 1970 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=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no 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 139A8C433E0 for ; Wed, 10 Feb 2021 13:21:44 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 9884964D92 for ; Wed, 10 Feb 2021 13:21:43 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9884964D92 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 1A7D66B0070; Wed, 10 Feb 2021 08:21:43 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 1581E6B0071; Wed, 10 Feb 2021 08:21:43 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 06E1B6B0072; Wed, 10 Feb 2021 08:21:43 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0118.hostedemail.com [216.40.44.118]) by kanga.kvack.org (Postfix) with ESMTP id E17CE6B0070 for ; Wed, 10 Feb 2021 08:21:42 -0500 (EST) Received: from smtpin25.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id B108B185B45D2 for ; Wed, 10 Feb 2021 13:21:42 +0000 (UTC) X-FDA: 77802420444.25.line82_5c0961227610 Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin25.hostedemail.com (Postfix) with ESMTP id 8AA5A185A3EA5 for ; Wed, 10 Feb 2021 13:21:42 +0000 (UTC) X-HE-Tag: line82_5c0961227610 X-Filterd-Recvd-Size: 1698 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by imf34.hostedemail.com (Postfix) with ESMTP for ; Wed, 10 Feb 2021 13:21:41 +0000 (UTC) Received: by verein.lst.de (Postfix, from userid 2407) id 9C95C68B02; Wed, 10 Feb 2021 14:21:39 +0100 (CET) Date: Wed, 10 Feb 2021 14:21:39 +0100 From: Christoph Hellwig To: Shiyang Ruan Cc: 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, darrick.wong@oracle.com, dan.j.williams@intel.com, david@fromorbit.com, hch@lst.de, agk@redhat.com, snitzer@redhat.com, rgoldwyn@suse.de, qi.fuli@fujitsu.com, y-goto@fujitsu.com Subject: Re: [PATCH v3 02/11] blk: Introduce ->corrupted_range() for block device Message-ID: <20210210132139.GC30109@lst.de> References: <20210208105530.3072869-1-ruansy.fnst@cn.fujitsu.com> <20210208105530.3072869-3-ruansy.fnst@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210208105530.3072869-3-ruansy.fnst@cn.fujitsu.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, Feb 08, 2021 at 06:55:21PM +0800, Shiyang Ruan wrote: > In fsdax mode, the memory failure happens on block device. So, it is > needed to introduce an interface for block devices. Each kind of block > device can handle the memory failure in ther own ways. As told before: DAX operations please do not add anything to the block device. We've been working very hard to decouple DAX from the block device, and while we're not done regressing the split should not happen.