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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 083D0C4332F for ; Wed, 5 Jan 2022 23:01:36 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 1F8DE6B0072; Wed, 5 Jan 2022 18:01:36 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 1A7EE6B0073; Wed, 5 Jan 2022 18:01:36 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 070906B0074; Wed, 5 Jan 2022 18:01:36 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0099.hostedemail.com [216.40.44.99]) by kanga.kvack.org (Postfix) with ESMTP id EC4AB6B0072 for ; Wed, 5 Jan 2022 18:01:35 -0500 (EST) Received: from smtpin29.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id AD38392EDC for ; Wed, 5 Jan 2022 23:01:35 +0000 (UTC) X-FDA: 78997756950.29.7FCDDD4 Received: from mail-pj1-f53.google.com (mail-pj1-f53.google.com [209.85.216.53]) by imf11.hostedemail.com (Postfix) with ESMTP id 429AB40010 for ; Wed, 5 Jan 2022 23:01:30 +0000 (UTC) Received: by mail-pj1-f53.google.com with SMTP id b1-20020a17090a990100b001b14bd47532so613174pjp.0 for ; Wed, 05 Jan 2022 15:01:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lYUQ0jogQjWg2SKVQ30dsRSlcaeazzEtqXlzWbNNuus=; b=6/Bg0iJxptBJ5muNxEYKrhAdId1eegrkiDTwzcOkRNG/1pZwpe1Kc0tU6bymS70DU+ 8ESBLtk3380N/aKA8dhXdtVbUKbQsElmA07znjldaLWcH03yYl0NJ+Q3XI9jXdeV+wTA qiCK76kfVGn9XvWsW5PPFXZDbq1/msVbB258rBMaV3S/YjxN4yci+XoYeyeBXenxbope yR2CxFbsnkQBSpIRlpWUkp2grrtqnY9HE9vcXNYsrBYd/F9pbY0XWdeUm3fL70Gb4cVx 1lwv7FgulwaSqIh8FBqTbxrhxp9I7C4OUgas3UZmtPvyetq/ZpjcVvDGItfdG8xgBLGW CJ0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lYUQ0jogQjWg2SKVQ30dsRSlcaeazzEtqXlzWbNNuus=; b=03y3dgvqd7jw1PpWzfoQa3PFpizAArJc52CqvbQ2mruI1C8kCfAurTUIjsn0XG7Xp5 ENuQ0RMH+FsHvr9KI70hj7NePaUOdnKWEfkrm1VyTACs7jvuUhzMN/ZTE+q4QQ20Thi8 9nV6lZttGj3Bl4TlWsdujoqSFrikv8Ab3hcvvp8ctg7ClHSDoG8M3rl5Yo3AlHmIND/V dlECKhXT5oOY+ttA/jF6HnOiACHpQ/IU+S7tYavvXGH50OKTiz2FbQeshWTpVN+Q8Zhj Rh7MxYW/m9g25xasZTnm/FuYglwUHLm1H0rQjkBFQPlAKTzS/I2tT/gLPRHZl3hD7htn /seg== X-Gm-Message-State: AOAM530HdvabmoS4hK2wax7/z/wtYFhs6Z5qkknrQYg5McyokhtF2nOH KDMW9XH0C4rRBv+9PSOIMaWuECJ7vzC/4VWHnwMPcA== X-Google-Smtp-Source: ABdhPJzf5eJTSEClLg5zwO6K5qaFfN5H8KDGlVe5p8PWRR8tnpS8qX7iqOl0I8aQyNguu6qYdaAdcFHeQgkO1dL21w0= X-Received: by 2002:a17:90a:e7cb:: with SMTP id kb11mr6739703pjb.8.1641423693104; Wed, 05 Jan 2022 15:01:33 -0800 (PST) MIME-Version: 1.0 References: <20211226143439.3985960-1-ruansy.fnst@fujitsu.com> <20211226143439.3985960-3-ruansy.fnst@fujitsu.com> <20220105181230.GC398655@magnolia> <20220105185626.GE398655@magnolia> <20220105224727.GG398655@magnolia> In-Reply-To: <20220105224727.GG398655@magnolia> From: Dan Williams Date: Wed, 5 Jan 2022 15:01:22 -0800 Message-ID: Subject: Re: [PATCH v9 02/10] dax: Introduce holder for dax_device To: "Darrick J. Wong" Cc: Shiyang Ruan , Linux Kernel Mailing List , linux-xfs , Linux NVDIMM , Linux MM , linux-fsdevel , david , Christoph Hellwig , Jane Chu Content-Type: text/plain; charset="UTF-8" X-Rspamd-Server: rspam09 X-Rspamd-Queue-Id: 429AB40010 X-Stat-Signature: sdtaurwd1brrxnqper8kp4h9g53dis4z Authentication-Results: imf11.hostedemail.com; dkim=pass header.d=intel-com.20210112.gappssmtp.com header.s=20210112 header.b="6/Bg0iJx"; spf=none (imf11.hostedemail.com: domain of dan.j.williams@intel.com has no SPF policy when checking 209.85.216.53) smtp.mailfrom=dan.j.williams@intel.com; dmarc=fail reason="No valid SPF, DKIM not aligned (relaxed)" header.from=intel.com (policy=none) X-HE-Tag: 1641423690-129550 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 Wed, Jan 5, 2022 at 2:47 PM Darrick J. Wong wrote: > > On Wed, Jan 05, 2022 at 11:20:12AM -0800, Dan Williams wrote: > > On Wed, Jan 5, 2022 at 10:56 AM Darrick J. Wong wrote: > > > > > > On Wed, Jan 05, 2022 at 10:23:08AM -0800, Dan Williams wrote: > > > > On Wed, Jan 5, 2022 at 10:12 AM Darrick J. Wong wrote: > > > > > > > > > > On Sun, Dec 26, 2021 at 10:34:31PM +0800, Shiyang Ruan wrote: > > > > > > To easily track filesystem from a pmem device, we introduce a holder for > > > > > > dax_device structure, and also its operation. This holder is used to > > > > > > remember who is using this dax_device: > > > > > > - When it is the backend of a filesystem, the holder will be the > > > > > > instance of this filesystem. > > > > > > - When this pmem device is one of the targets in a mapped device, the > > > > > > holder will be this mapped device. In this case, the mapped device > > > > > > has its own dax_device and it will follow the first rule. So that we > > > > > > can finally track to the filesystem we needed. > > > > > > > > > > > > The holder and holder_ops will be set when filesystem is being mounted, > > > > > > or an target device is being activated. > > > > > > > > > > > > Signed-off-by: Shiyang Ruan > > > > > > --- > > > > > > drivers/dax/super.c | 62 +++++++++++++++++++++++++++++++++++++++++++++ > > > > > > include/linux/dax.h | 29 +++++++++++++++++++++ > > > > > > 2 files changed, 91 insertions(+) > > > > > > > > > > > > diff --git a/drivers/dax/super.c b/drivers/dax/super.c > > > > > > index c46f56e33d40..94c51f2ee133 100644 > > > > > > --- a/drivers/dax/super.c > > > > > > +++ b/drivers/dax/super.c > > > > > > @@ -20,15 +20,20 @@ > > > > > > * @inode: core vfs > > > > > > * @cdev: optional character interface for "device dax" > > > > > > * @private: dax driver private data > > > > > > + * @holder_data: holder of a dax_device: could be filesystem or mapped device > > > > > > * @flags: state and boolean properties > > > > > > + * @ops: operations for dax_device > > > > > > + * @holder_ops: operations for the inner holder > > > > > > */ > > > > > > struct dax_device { > > > > > > struct inode inode; > > > > > > struct cdev cdev; > > > > > > void *private; > > > > > > struct percpu_rw_semaphore rwsem; > > > > > > + void *holder_data; > > > > > > unsigned long flags; > > > > > > const struct dax_operations *ops; > > > > > > + const struct dax_holder_operations *holder_ops; > > > > > > }; > > > > > > > > > > > > static dev_t dax_devt; > > > > > > @@ -192,6 +197,29 @@ int dax_zero_page_range(struct dax_device *dax_dev, pgoff_t pgoff, > > > > > > } > > > > > > EXPORT_SYMBOL_GPL(dax_zero_page_range); > > > > > > > > > > > > +int dax_holder_notify_failure(struct dax_device *dax_dev, u64 off, > > > > > > + u64 len, int mf_flags) > > > > > > +{ > > > > > > + int rc; > > > > > > + > > > > > > + dax_read_lock(dax_dev); > > > > > > + if (!dax_alive(dax_dev)) { > > > > > > + rc = -ENXIO; > > > > > > + goto out; > > > > > > + } > > > > > > + > > > > > > + if (!dax_dev->holder_ops) { > > > > > > + rc = -EOPNOTSUPP; > > > > > > + goto out; > > > > > > + } > > > > > > + > > > > > > + rc = dax_dev->holder_ops->notify_failure(dax_dev, off, len, mf_flags); > > > > > > +out: > > > > > > + dax_read_unlock(dax_dev); > > > > > > + return rc; > > > > > > +} > > > > > > +EXPORT_SYMBOL_GPL(dax_holder_notify_failure); > > > > > > + > > > > > > #ifdef CONFIG_ARCH_HAS_PMEM_API > > > > > > void arch_wb_cache_pmem(void *addr, size_t size); > > > > > > void dax_flush(struct dax_device *dax_dev, void *addr, size_t size) > > > > > > @@ -254,6 +282,10 @@ void kill_dax(struct dax_device *dax_dev) > > > > > > return; > > > > > > dax_write_lock(dax_dev); > > > > > > clear_bit(DAXDEV_ALIVE, &dax_dev->flags); > > > > > > + > > > > > > + /* clear holder data */ > > > > > > + dax_dev->holder_ops = NULL; > > > > > > + dax_dev->holder_data = NULL; > > > > > > dax_write_unlock(dax_dev); > > > > > > } > > > > > > EXPORT_SYMBOL_GPL(kill_dax); > > > > > > @@ -401,6 +433,36 @@ void put_dax(struct dax_device *dax_dev) > > > > > > } > > > > > > EXPORT_SYMBOL_GPL(put_dax); > > > > > > > > > > > > +void dax_register_holder(struct dax_device *dax_dev, void *holder, > > > > > > + const struct dax_holder_operations *ops) > > > > > > +{ > > > > > > + if (!dax_alive(dax_dev)) > > > > > > + return; > > > > > > + > > > > > > + dax_dev->holder_data = holder; > > > > > > + dax_dev->holder_ops = ops; > > > > > > > > > > Shouldn't this return an error code if the dax device is dead or if > > > > > someone already registered a holder? I'm pretty sure XFS should not > > > > > bind to a dax device if someone else already registered for it... > > > > > > > > Agree, yes. > > > > > > > > > > > > > > ...unless you want to use a notifier chain for failure events so that > > > > > there can be multiple consumers of dax failure events? > > > > > > > > No, I would hope not. It should be 1:1 holders to dax-devices. Similar > > > > ownership semantics like bd_prepare_to_claim(). > > > > > > Does each partition on a pmem device still have its own dax_device? > > > > No, it never did... > > > > Just as before, each dax-device is still associated with a gendisk / > > whole-block_device. The recent change is that instead of needing that > > partition-block_device plumbed to convert a relative block number to > > its absolute whole-block_device offset the filesystem now handles that > > at iomap_begin() time. See: > > > > if (mapping_flags & IOMAP_DAX) > > iomap->addr += target->bt_dax_part_off; > > > > ...in xfs_bmbt_to_iomap() (in -next). I.e. bdev_dax_pgoff() is gone > > with the lead-in reworks. > > OH. Crap, Dan's right: > > XFS (pmem0p1): ddev dax = 0xffff88800304ed00 bdev = 0xffff8880480d6180 > XFS (pmem0p2): ddev dax = 0xffff88800304ed00 bdev = 0xffff8880480d4380 > > Unless you're planning to remove partition support too, this patch needs > to be reworked so that multiple filesystems in separate partitions can > each call dax_register_holder to receive memory_failure notifications > for their partition. Oh, crap indeed. I think this gets back to the slow tip-toeing away from dax + partition support. While FSDAX can continue to support "legacy/experimental" operation on partitions of DAX capable block devices, I think failure notification + reflink support is where we draw the line and say "DAX on partitions was a mistake, it's too late to undo that mistake, but going forward for new FSDAX features it requires switching from block-device partitions to pmem-namespaces if you need sub-division support and new DAX features." > /methinks this sharing is all a little scary... Yes, I think we should just fail the holder registration and DAX+reflink unless the FS being mounted on a whole device. I know Ted and others had reservations about moving filesystems to be mounted on dax-devices directly, but hopefully the whole-block_device requirement is a workable middle ground?