[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMZfGtUb+xF9nFd21g8tagjRTCYg7R=HOVmXvVZhbtx8im3FDQ@mail.gmail.com>
Date: Mon, 24 Jan 2022 17:07:38 +0800
From: Muchun Song <songmuchun@...edance.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Dan Williams <dan.j.williams@...el.com>,
Matthew Wilcox <willy@...radead.org>, Jan Kara <jack@...e.cz>,
Alexander Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>, apopple@...dia.com,
Yang Shi <shy828301@...il.com>, rcampbell@...dia.com,
Hugh Dickins <hughd@...gle.com>,
Xiyu Yang <xiyuyang19@...an.edu.cn>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
zwisler@...nel.org, linux-fsdevel <linux-fsdevel@...r.kernel.org>,
nvdimm@...ts.linux.dev, LKML <linux-kernel@...r.kernel.org>,
Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: [PATCH 4/5] dax: fix missing writeprotect the pte entry
On Mon, Jan 24, 2022 at 3:41 PM Christoph Hellwig <hch@...radead.org> wrote:
>
> 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?
Will do. I'll introduce page_vma_mkclean_one in a prepared patch
and then fix the DAX issue in a separate patch. Thanks for your
suggestions.
>
> > + 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.
>
Will do.
Thanks.
Powered by blists - more mailing lists