[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ye5YNbBbVymwfPB0@infradead.org>
Date: Sun, 23 Jan 2022 23:41:41 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Muchun Song <songmuchun@...edance.com>
Cc: dan.j.williams@...el.com, willy@...radead.org, jack@...e.cz,
viro@...iv.linux.org.uk, akpm@...ux-foundation.org,
apopple@...dia.com, shy828301@...il.com, rcampbell@...dia.com,
hughd@...gle.com, xiyuyang19@...an.edu.cn,
kirill.shutemov@...ux.intel.com, zwisler@...nel.org,
linux-fsdevel@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 4/5] dax: fix missing writeprotect the pte entry
On Fri, Jan 21, 2022 at 03:55:14PM +0800, Muchun Song wrote:
> Reuse some infrastructure of page_mkclean_one() to let DAX can handle
> similar case to fix this issue.
Can you split out some of the infrastructure changes into proper
well-documented preparation patches?
> + pgoff_t pgoff_end = pgoff_start + npfn - 1;
>
> i_mmap_lock_read(mapping);
> - vma_interval_tree_foreach(vma, &mapping->i_mmap, index, index) {
> - struct mmu_notifier_range range;
> - unsigned long address;
> -
> + vma_interval_tree_foreach(vma, &mapping->i_mmap, pgoff_start, pgoff_end) {
Please avoid the overly long lines here. Just using start and end
might be an easy option.
Powered by blists - more mailing lists