From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm@lists.01.org, Dave Chinner <david@fromorbit.com>,
stable@vger.kernel.org, linux-block@vger.kernel.org,
Jan Kara <jack@suse.com>,
linux-fsdevel@vger.kernel.org, willy@linux.intel.com,
ross.zwisler@linux.intel.com, akpm@linux-foundation.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH 2/8] dax: disable pmd mappings
Date: Tue, 17 Nov 2015 13:51:20 -0700 [thread overview]
Message-ID: <20151117205120.GF28024@linux.intel.com> (raw)
In-Reply-To: <20151117201603.15053.77916.stgit@dwillia2-desk3.jf.intel.com>
On Tue, Nov 17, 2015 at 12:16:03PM -0800, Dan Williams wrote:
> While dax pmd mappings are functional in the nominal path they trigger
> kernel crashes in the following paths:
>
> BUG: unable to handle kernel paging request at ffffea0004098000
> IP: [<ffffffff812362f7>] follow_trans_huge_pmd+0x117/0x3b0
> [..]
> Call Trace:
> [<ffffffff811f6573>] follow_page_mask+0x2d3/0x380
> [<ffffffff811f6708>] __get_user_pages+0xe8/0x6f0
> [<ffffffff811f7045>] get_user_pages_unlocked+0x165/0x1e0
> [<ffffffff8106f5b1>] get_user_pages_fast+0xa1/0x1b0
>
> kernel BUG at arch/x86/mm/gup.c:131!
> [..]
> Call Trace:
> [<ffffffff8106f34c>] gup_pud_range+0x1bc/0x220
> [<ffffffff8106f634>] get_user_pages_fast+0x124/0x1b0
>
> BUG: unable to handle kernel paging request at ffffea0004088000
> IP: [<ffffffff81235f49>] copy_huge_pmd+0x159/0x350
> [..]
> Call Trace:
> [<ffffffff811fad3c>] copy_page_range+0x34c/0x9f0
> [<ffffffff810a0daf>] copy_process+0x1b7f/0x1e10
> [<ffffffff810a11c1>] _do_fork+0x91/0x590
>
> All of these paths are interpreting a dax pmd mapping as a transparent
> huge page and making the assumption that the pfn is covered by the
> memmap, i.e. that the pfn has an associated struct page. PTE mappings
> do not suffer the same fate since they have the _PAGE_SPECIAL flag to
> cause the gup path to fault. We can do something similar for the PMD
> path, or otherwise defer pmd support for cases where a struct page is
> available. For now, 4.4-rc and -stable need to disable dax pmd support
> by default.
>
> For development the "depends on BROKEN" line can be removed from
> CONFIG_FS_DAX_PMD.
>
> Cc: <stable@vger.kernel.org>
> Cc: Jan Kara <jack@suse.com>
> Cc: Dave Chinner <david@fromorbit.com>
> Cc: Matthew Wilcox <willy@linux.intel.com>
> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Reported-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Acked-by: Ross Zwisler <ross.zwisler@linux.intel.com>
next prev parent reply other threads:[~2015-11-17 20:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 20:15 [PATCH 0/8] dax fixes / cleanups: pmd vs thp, lifetime, and locking Dan Williams
2015-11-17 20:15 ` [PATCH 1/8] ext2, ext4: warn when mounting with dax enabled Dan Williams
2015-11-17 20:16 ` [PATCH 2/8] dax: disable pmd mappings Dan Williams
2015-11-17 20:51 ` Ross Zwisler [this message]
2015-11-17 20:16 ` [PATCH 3/8] mm, dax: fix DAX deadlocks (COW fault) Dan Williams
2015-11-17 20:16 ` [PATCH 4/8] mm, dax: truncate dax mappings at bdev or fs shutdown Dan Williams
2015-11-18 15:09 ` Jan Kara
2015-11-19 0:22 ` Williams, Dan J
2015-11-19 12:55 ` Jan Kara
2015-11-19 16:55 ` Dan Williams
2015-11-19 17:12 ` Jan Kara
2015-11-19 23:17 ` Dave Chinner
2015-11-20 0:05 ` Williams, Dan J
2015-11-20 4:06 ` Dave Chinner
2015-11-20 4:25 ` Dan Williams
2015-11-20 17:08 ` Dan Williams
2015-11-17 20:16 ` [PATCH 5/8] pmem, dax: clean up clear_pmem() Dan Williams
2015-11-17 20:16 ` [PATCH 6/8] dax: increase granularity of dax_clear_blocks() operations Dan Williams
2015-11-17 20:16 ` [PATCH 7/8] dax: guarantee page aligned results from bdev_direct_access() Dan Williams
2015-11-17 20:16 ` [PATCH 8/8] dax: fix lifetime of in-kernel dax mappings with dax_map_atomic() 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=20151117205120.GF28024@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=jack@suse.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=stable@vger.kernel.org \
--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.