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 77614C433F5 for ; Wed, 16 Feb 2022 01:34:22 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 8B3EE6B0071; Tue, 15 Feb 2022 20:34:21 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 8645B6B0073; Tue, 15 Feb 2022 20:34:21 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 704926B0078; Tue, 15 Feb 2022 20:34:21 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0218.hostedemail.com [216.40.44.218]) by kanga.kvack.org (Postfix) with ESMTP id 5C9DE6B0071 for ; Tue, 15 Feb 2022 20:34:21 -0500 (EST) Received: from smtpin14.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 17949180ACF6C for ; Wed, 16 Feb 2022 01:34:21 +0000 (UTC) X-FDA: 79146922722.14.872C1F1 Received: from mail-pg1-f178.google.com (mail-pg1-f178.google.com [209.85.215.178]) by imf18.hostedemail.com (Postfix) with ESMTP id A83FC1C0004 for ; Wed, 16 Feb 2022 01:34:20 +0000 (UTC) Received: by mail-pg1-f178.google.com with SMTP id 195so766411pgc.6 for ; Tue, 15 Feb 2022 17:34:20 -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=vvTayVguxhrumT3w+R+Kjfmd3diECndIkorPQyxblp0=; b=NFjoQ+hOdtNnkcduj0LnOAfr0t13qJU0g+H3qDYhxHXNY2kSOBhjJ57id3nggkZ63z bd+0no5Sz1hfOpOM7FqU7/lcj3mw/zA9iIJGXn1/3gABVkhTJwDuVFXiLCiF+AoiAuvP xzHa0AMAlBDyRB3g8rVKOe7JL6peWAms2JmtnTljT+4i1CykaarkkcY2Phufrs+l4f98 tIBmQaYCJwnUN4p1EvcyxZr3Y2TIDezPhrxlygMSyqcqJutwde5Wmrbzs8FUsbjeBtAE KAXJkvUlQ4SnUi7Ml0QZWal8mO29LLZbB5qS5ZaYGR1b1d2ZM10qVKD8leaATzhRe6MQ OvXg== 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=vvTayVguxhrumT3w+R+Kjfmd3diECndIkorPQyxblp0=; b=YW7pBBt26flUPT+by6R9zUilm0X6Dg+sEh/mBFKE/f1zn+T8xBgvJ5lr3DD1zUcq3J 926GdV/Kzl9tkg21c1hCWqG4iy5bJO95OvJlg6IfXINxOmu6P7tpqCcEnMtOEqHDjQwE OOlyVnbltv3wga3SYXU77eCxCkvsZOShnZhf6qXkusu/4gP5hbCSHp0me2z2/Y/wX4VS HlEEGTSjSLSm5hKmp+HQapAlQZWY93AhxelpA8hrr7yqr5qsm+39LK3WGlaiwRxjy0MK vTeYiahR1g8W44FZHfdWxCMQ0FaJsMfwBePnV3jfBhyWKvd2ZXNpLOKxWRo9hFPx34xu HOcg== X-Gm-Message-State: AOAM531OHu0QO7aAlcep9bXNijXF5/x+r7uV7oELNuNa1wnS8PDbF8sQ WoOrlM2/+hYXjCNHQT/pPQItzel+orF5DDf2DI1K1g== X-Google-Smtp-Source: ABdhPJzAqkHS4nuPDQC4F8eXmkoN7S6evLhsGsn+9OiK2Onw6wqEebsZdEzEmmlrTDiHX9fR4bL6Yj1AYLHUkW1bqes= X-Received: by 2002:a05:6a02:283:b0:342:703e:1434 with SMTP id bk3-20020a056a02028300b00342703e1434mr370669pgb.74.1644975259581; Tue, 15 Feb 2022 17:34:19 -0800 (PST) MIME-Version: 1.0 References: <20220127124058.1172422-1-ruansy.fnst@fujitsu.com> <20220127124058.1172422-6-ruansy.fnst@fujitsu.com> In-Reply-To: <20220127124058.1172422-6-ruansy.fnst@fujitsu.com> From: Dan Williams Date: Tue, 15 Feb 2022 17:34:12 -0800 Message-ID: Subject: Re: [PATCH v10 5/9] fsdax: Introduce dax_load_page() To: Shiyang Ruan Cc: Linux Kernel Mailing List , linux-xfs , Linux NVDIMM , Linux MM , linux-fsdevel , "Darrick J. Wong" , david , Christoph Hellwig , Jane Chu , Christoph Hellwig Content-Type: text/plain; charset="UTF-8" X-Stat-Signature: hy55homw95m5c7hpkxipoi6mek3n4gtr X-Rspamd-Server: rspam02 X-Rspamd-Queue-Id: A83FC1C0004 Authentication-Results: imf18.hostedemail.com; dkim=pass header.d=intel-com.20210112.gappssmtp.com header.s=20210112 header.b=NFjoQ+hO; dmarc=fail reason="No valid SPF, DKIM not aligned (relaxed)" header.from=intel.com (policy=none); spf=none (imf18.hostedemail.com: domain of dan.j.williams@intel.com has no SPF policy when checking 209.85.215.178) smtp.mailfrom=dan.j.williams@intel.com X-Rspam-User: X-HE-Tag: 1644975260-639547 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 Thu, Jan 27, 2022 at 4:41 AM Shiyang Ruan wrote: > > The current dax_lock_page() locks dax entry by obtaining mapping and > index in page. To support 1-to-N RMAP in NVDIMM, we need a new function > to lock a specific dax entry I do not see a call to dax_lock_entry() in this function, what keeps this lookup valid after xas_unlock_irq()?