[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4jWuWWWBAEesMorK+LL6GVyqf-=VSChdw6P8txtckC=aw@mail.gmail.com>
Date: Tue, 15 Feb 2022 17:34:12 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: Shiyang Ruan <ruansy.fnst@...itsu.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-xfs <linux-xfs@...r.kernel.org>,
Linux NVDIMM <nvdimm@...ts.linux.dev>,
Linux MM <linux-mm@...ck.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
"Darrick J. Wong" <djwong@...nel.org>, david <david@...morbit.com>,
Christoph Hellwig <hch@...radead.org>,
Jane Chu <jane.chu@...cle.com>, Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v10 5/9] fsdax: Introduce dax_load_page()
On Thu, Jan 27, 2022 at 4:41 AM Shiyang Ruan <ruansy.fnst@...itsu.com> 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()?
Powered by blists - more mailing lists