All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Dan Williams <dan.j.williams@intel.com>, ^[^[@linux.intel.com
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Matthew Wilcox <willy@linux.intel.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	Dave Chinner <david@fromorbit.com>, Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v2] dax: fix NULL pointer in __dax_pmd_fault()
Date: Tue, 22 Sep 2015 15:17:16 -0600	[thread overview]
Message-ID: <20150922211716.GA32623@linux.intel.com> (raw)
In-Reply-To: <CAPcyv4hubJDhWResqaG_aQLSLUVEOujk=EEDVQ1BF+sAdK45LA@mail.gmail.com>

On Tue, Sep 22, 2015 at 01:51:04PM -0700, Dan Williams wrote:
> [ adding Andrew ]
> 
> On Tue, Sep 22, 2015 at 12:36 PM, Ross Zwisler
> <ross.zwisler@linux.intel.com> wrote:
> > The following commit:
> >
> > commit 46c043ede471 ("mm: take i_mmap_lock in unmap_mapping_range() for
> >         DAX")
> >
> > moved some code in __dax_pmd_fault() that was responsible for zeroing
> > newly allocated PMD pages.  The new location didn't properly set up
> > 'kaddr', though, so when run this code resulted in a NULL pointer BUG.
> >
> > Fix this by getting the correct 'kaddr' via bdev_direct_access().
> >
> > Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> > Reported-by: Dan Williams <dan.j.williams@intel.com>
> 
> Taking into account the comment below,
> 
> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
> 
> > ---
> >  fs/dax.c | 13 ++++++++++++-
> >  1 file changed, 12 insertions(+), 1 deletion(-)
> >
> > diff --git a/fs/dax.c b/fs/dax.c
> > index 7ae6df7..bcfb14b 100644
> > --- a/fs/dax.c
> > +++ b/fs/dax.c
> > @@ -569,8 +569,20 @@ int __dax_pmd_fault(struct vm_area_struct *vma, unsigned long address,
> >         if (!buffer_size_valid(&bh) || bh.b_size < PMD_SIZE)
> >                 goto fallback;
> >
> > +       sector = bh.b_blocknr << (blkbits - 9);
> > +
> >         if (buffer_unwritten(&bh) || buffer_new(&bh)) {
> >                 int i;
> > +
> > +               length = bdev_direct_access(bh.b_bdev, sector, &kaddr, &pfn,
> > +                                               bh.b_size);
> > +               if (length < 0) {
> > +                       result = VM_FAULT_SIGBUS;
> > +                       goto out;
> > +               }
> > +               if ((length < PMD_SIZE) || (pfn & PG_PMD_COLOUR))
> > +                       goto fallback;
> > +
> 
> Hmm, we don't need the PG_PMD_COLOUR check since we aren't using the
> pfn in this path, right?

I think we care, because we'll end up bailing anyway at the later
PG_PMD_COLOUR check before we actually insert the pfn via
vmf_insert_pfn_pmd().  If we don't check the alignment we'll do 2 MiB worth of
zeroing to the media, then later fall back to PTE faults.

--
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>

  reply	other threads:[~2015-09-22 21:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 19:36 [PATCH v2] dax: fix NULL pointer in __dax_pmd_fault() Ross Zwisler
2015-09-22 19:36 ` Ross Zwisler
2015-09-22 20:51 ` Dan Williams
2015-09-22 20:51   ` Dan Williams
2015-09-22 20:51   ` Dan Williams
2015-09-22 21:17   ` Ross Zwisler [this message]
2015-09-22 21:26     ` Dan Williams
2015-09-22 21:26       ` Dan Williams
2015-09-22 21:26       ` Dan Williams
2015-09-22 21:13 ` Andrew Morton
2015-09-22 21:25   ` Dan Williams
2015-09-22 23:30     ` Dave Chinner
2015-09-23  3:00       ` Dan Williams
2015-09-23  9:04         ` Dave Chinner
2015-09-24  8:50           ` Boaz Harrosh
2015-09-24 16:06           ` Dan Williams

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=20150922211716.GA32623@linux.intel.com \
    --to=ross.zwisler@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=david@fromorbit.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@lists.01.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.