diff options
| author | Dave Jiang <dave.jiang@intel.com> | 2018-09-04 15:46:16 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-09-04 16:45:02 -0700 |
| commit | 62ec0d8c4f332dedf19d6fad15ddea639044d5fe (patch) | |
| tree | a405529e5c9840eb4d321ff6172b5c14e8a9de0f /scripts | |
| parent | 8a2336e549d385bb0b46880435b411df8d8200e8 (diff) | |
| download | linux-stable-62ec0d8c4f332dedf19d6fad15ddea639044d5fe.tar.gz linux-stable-62ec0d8c4f332dedf19d6fad15ddea639044d5fe.tar.bz2 linux-stable-62ec0d8c4f332dedf19d6fad15ddea639044d5fe.zip | |
mm: fix BUG_ON() in vmf_insert_pfn_pud() from VM_MIXEDMAP removal
It looks like I missed the PUD path when doing VM_MIXEDMAP removal.
This can be triggered by:
1. Boot with memmap=4G!8G
2. build ndctl with destructive flag on
3. make TESTS=device-dax check
[ +0.000675] kernel BUG at mm/huge_memory.c:824!
Applying the same change that was applied to vmf_insert_pfn_pmd() in the
original patch.
Link: http://lkml.kernel.org/r/153565957352.35524.1005746906902065126.stgit@djiang5-desk3.ch.intel.com
Fixes: e1fb4a08649 ("dax: remove VM_MIXEDMAP for fsdax and device dax")
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Reported-by: Vishal Verma <vishal.l.verma@intel.com>
Tested-by: Vishal Verma <vishal.l.verma@intel.com>
Acked-by: Jeff Moyer <jmoyer@redhat.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions