From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Matthew Wilcox <matthew.r.wilcox@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
ross.zwisler@linux.intel.com
Subject: Re: [PATCH] mm: take i_mmap_lock in unmap_mapping_range() for DAX
Date: Wed, 16 Sep 2015 14:12:18 +0300 [thread overview]
Message-ID: <20150916111218.GB23026@node.dhcp.inet.fi> (raw)
In-Reply-To: <CAA9_cmd9D=7YgZrCf+w3HcckoqcfmCLEHhhm9j+kv+V0ijUnqw@mail.gmail.com>
On Tue, Sep 15, 2015 at 04:52:42PM -0700, Dan Williams wrote:
> Hi Kirill,
>
> On Fri, Aug 7, 2015 at 4:53 AM, Kirill A. Shutemov
> <kirill.shutemov@linux.intel.com> wrote:
> > DAX is not so special: we need i_mmap_lock to protect mapping->i_mmap.
> >
> > __dax_pmd_fault() uses unmap_mapping_range() shoot out zero page from
> > all mappings. We need to drop i_mmap_lock there to avoid lock deadlock.
> >
> > Re-aquiring the lock should be fine since we check i_size after the
> > point.
> >
> > Not-yet-signed-off-by: Matthew Wilcox <willy@linux.intel.com>
> > Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> > ---
> > fs/dax.c | 35 +++++++++++++++++++----------------
> > mm/memory.c | 11 ++---------
> > 2 files changed, 21 insertions(+), 25 deletions(-)
> >
> > diff --git a/fs/dax.c b/fs/dax.c
> > index 9ef9b80cc132..ed54efedade6 100644
> > --- a/fs/dax.c
> > +++ b/fs/dax.c
> > @@ -554,6 +554,25 @@ int __dax_pmd_fault(struct vm_area_struct *vma, unsigned long address,
> > if (!buffer_size_valid(&bh) || bh.b_size < PMD_SIZE)
> > goto fallback;
> >
> > + if (buffer_unwritten(&bh) || buffer_new(&bh)) {
> > + int i;
> > + for (i = 0; i < PTRS_PER_PMD; i++)
> > + clear_page(kaddr + i * PAGE_SIZE);
>
> This patch, now upstream as commit 46c043ede471, moves the call to
> clear_page() earlier in __dax_pmd_fault(). However, 'kaddr' is not
> set at this point, so I'm not sure this path was ever tested.
Ughh. It's obviously broken.
I took fs/dax.c part of the patch from Matthew. And I'm not sure now we
would need to move this "if (buffer_unwritten(&bh) || buffer_new(&bh)) {"
block around. It should work fine where it was before. Right?
Matthew?
> I'm also not sure why the compiler is not complaining about an
> uninitialized variable?
No idea.
--
Kirill A. Shutemov
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-09-16 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 11:53 [PATCH] mm: take i_mmap_lock in unmap_mapping_range() for DAX Kirill A. Shutemov
2015-09-15 23:52 ` Dan Williams
2015-09-16 11:12 ` Kirill A. Shutemov [this message]
2015-09-17 15:41 ` Ross Zwisler
2015-09-17 15:46 ` Dan Williams
2015-09-17 15:47 ` Kirill A. Shutemov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150916111218.GB23026@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=matthew.r.wilcox@intel.com \
--cc=ross.zwisler@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).