Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp124155pxb; Tue, 12 Apr 2022 18:52:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz1iT8id0eCpVe0HSdi+gTAIxptCua9UhFFIkpGfx1t3akXfQeEvfO52WAZsQPjYOmuggde X-Received: by 2002:a17:907:1693:b0:6e8:c7e5:c297 with SMTP id hc19-20020a170907169300b006e8c7e5c297mr933278ejc.138.1649814727171; Tue, 12 Apr 2022 18:52:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649814727; cv=none; d=google.com; s=arc-20160816; b=p5D+6PmOKAQEJW5afYe734z00an2S1nku7a9Hxd+ytg6AvX2NIsWsgfay7eR/BFMmU 30RdZeaQBw45YX1KLuN5XP6xn8uOawgDiSLupLA+ryoI3+VzdMsxPUDFKIYvzZcqLsMG Em5i1ps9zDGlF84lz8Tojcsbf8iurWGBvQTci7ROGUH0NLTcpPc0373n3LW6APz/CXIC 0uKB5zDIXUQs1xszyFFOXUvPOladR4sBFmAd1fg6STvkp/ZSn1gNihA0DvCaCpZAKNIN N9oLSdk4x42z3V8CEuqPVdrttaPPkHxFufqfhJejXAvWPcD/BO3jl79paiQe+aIm9g49 8QkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=cXG2uBz6lRa6SmsxOh4UHnvAS1v6j3gtk2oaRONS+x4=; b=GZhtPrLKMUZ941ABv0XHy9mbfOXm3ymwMO/NYjKRyI8QuOZvTjob3B2z+X46suWdGK H0QUXQKpCi7G0I+uJrYkYeGcTZn5ZaENZoCZW8IV1uTTMbvx+M/xlfl9DXbAkW6mRs3U 5eGj0e2oYKyzDvgryFMXWjl6LvBKR0wSPnRthX7JT3cnzEPq6DxaNWDQyQZnb+Upa76T 2qHFeHV505vdYlC37YbkRwTJmWakl0771Wlv1lQ8a86yXAUcT1Wm5+37ie1XnCIZp1DG pNs1HYZvg0yP01A7l/eniR8MC9peKV9Do6clxt9A/24orDVlXmSRttPvG+uSxqLgmq20 SHSw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel-com.20210112.gappssmtp.com header.s=20210112 header.b=VPl1Lq9j; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m26-20020aa7c2da000000b0041cc318987fsi650253edp.550.2022.04.12.18.51.41; Tue, 12 Apr 2022 18:52:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel-com.20210112.gappssmtp.com header.s=20210112 header.b=VPl1Lq9j; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231204AbiDLXlI (ORCPT + 99 others); Tue, 12 Apr 2022 19:41:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60516 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231280AbiDLXk6 (ORCPT ); Tue, 12 Apr 2022 19:40:58 -0400 Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 24373AACA4 for ; Tue, 12 Apr 2022 16:22:46 -0700 (PDT) Received: by mail-oi1-x235.google.com with SMTP id b188so308030oia.13 for ; Tue, 12 Apr 2022 16:22:46 -0700 (PDT) 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=cXG2uBz6lRa6SmsxOh4UHnvAS1v6j3gtk2oaRONS+x4=; b=VPl1Lq9jWUOfdQHl/1KZuWWM6wCjlya9ZIm56mGgKOGxFiC5BaCc1BSVeUdc1pyItB BIIRsGb7m/uTTFP7EQ9bwdIRf6Qc2mw3gELQG2VwZAg2xJ2tVel9MI1+ME9SUoGaJ8Ck Z8ts0Cz8Sv7S9Fzd/Im/JfbGqbs45u5Dpd4A8hT36LVn0vEKF5gJNhz9Xj3HxeT5GFx9 3orzrVLxvjY3XUMpiLuJPsctZxiLUWVgCZp6UZHqMNblOrfxFCYbsUPAtL6PjFLKvIYv yR16Pm/ZW/nafNyxKUqk8z/2UQ0ECbaF4NEyEpOJWqi+m9FgHi5wKcizOSX3GGI9F65b O8Bw== 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=cXG2uBz6lRa6SmsxOh4UHnvAS1v6j3gtk2oaRONS+x4=; b=Tercn0nlL+s6g/AI+lcdTn0bDs60nzpJy7M0secDSA0c99JwH5axS/PSnGHPC2fgUQ ALUx3MHHQ/+hk8NejKZx+usaSqQ0/xaL1SwjcY5uY2KgmyE6BoTRJmU5E36QsLQwwK5g hVrM09GX+j3gWG3Qj4qIBipFBIq0thLT67gYp9P3w8ZiTHf9DJAD//SgDWNVxNUjOKSR eRZsGfbOEdIzIi0SkjVGcB7yUggoboPvoeQDflb4xi3rOuMKubcrCKV808ZwlUz309xC PJyyN2hOuqw5rws9qPHpUqDjL3D5Rz45t36wB24uIkn30kThwl4hyDYjFINAbNPAzFID S6gQ== X-Gm-Message-State: AOAM532B7s0ttFoyyrZeqBuzBSFV81UyOdMXM85TF9Aj8epdK0pZ6fnv 9erux+3uqI0sSPjFrLt0tERCN//0uaErtDmwo+ahhw== X-Received: by 2002:a05:6808:1154:b0:2da:2fbd:eba9 with SMTP id u20-20020a056808115400b002da2fbdeba9mr2979048oiu.133.1649805765445; Tue, 12 Apr 2022 16:22:45 -0700 (PDT) MIME-Version: 1.0 References: <20220410160904.3758789-1-ruansy.fnst@fujitsu.com> <20220410160904.3758789-2-ruansy.fnst@fujitsu.com> In-Reply-To: <20220410160904.3758789-2-ruansy.fnst@fujitsu.com> From: Dan Williams Date: Tue, 12 Apr 2022 16:22:34 -0700 Message-ID: Subject: Re: [PATCH v12 1/7] dax: Introduce holder for dax_device To: Shiyang Ruan Cc: Linux Kernel Mailing List , linux-xfs , Linux NVDIMM , Linux MM , linux-fsdevel , "Darrick J. Wong" , david , Christoph Hellwig , Jane Chu Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Apr 10, 2022 at 9:09 AM 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. > Looks good to me: Reviewed-by: Dan Williams I am assuming this will be staged in a common DAX branch, but holler now if this should go through the XFS tree.