From: kbuild test robot <lkp@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: kbuild-all@01.org, xfs@oss.sgi.com,
linux-fsdevel@vger.kernel.org, ross.zwisler@linux.intel.com,
willy@linux.intel.com, dan.j.williams@intel.com,
kirill.shutemov@linux.intel.com, linux-nvdimm@lists.01.org,
jack@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] Revert "mm: take i_mmap_lock in unmap_mapping_range() for DAX"
Date: Thu, 1 Oct 2015 16:35:50 +0800 [thread overview]
Message-ID: <201510011627.eAfVmtFF%fengguang.wu@intel.com> (raw)
In-Reply-To: <1443685599-4843-2-git-send-email-david@fromorbit.com>
Hi Dave,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> fs/dax.c:626:50: sparse: incorrect type in argument 1 (different address spaces)
fs/dax.c:626:50: expected void *page
fs/dax.c:626:50: got void [noderef] <asn:5>*
vim +626 fs/dax.c
610 result = VM_FAULT_NOPAGE;
611 spin_unlock(ptl);
612 } else {
613 sector = bh.b_blocknr << (blkbits - 9);
614 length = bdev_direct_access(bh.b_bdev, sector, &kaddr, &pfn,
615 bh.b_size);
616 if (length < 0) {
617 result = VM_FAULT_SIGBUS;
618 goto out;
619 }
620 if ((length < PMD_SIZE) || (pfn & PG_PMD_COLOUR))
621 goto fallback;
622
623 if (buffer_unwritten(&bh) || buffer_new(&bh)) {
624 int i;
625 for (i = 0; i < PTRS_PER_PMD; i++)
> 626 clear_page(kaddr + i * PAGE_SIZE);
627 count_vm_event(PGMAJFAULT);
628 mem_cgroup_count_vm_event(vma->vm_mm, PGMAJFAULT);
629 result |= VM_FAULT_MAJOR;
630 }
631
632 result |= vmf_insert_pfn_pmd(vma, address, pmd, pfn, write);
633 }
634
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2015-10-01 8:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 7:46 [PATCH 0/7] xfs, dax: fix the page fault/allocation mess Dave Chinner
2015-10-01 7:46 ` [PATCH 1/7] Revert "mm: take i_mmap_lock in unmap_mapping_range() for DAX" Dave Chinner
2015-10-01 8:35 ` kbuild test robot [this message]
2015-10-01 20:27 ` Ross Zwisler
2015-10-01 22:14 ` Williams, Dan J
2015-10-01 22:45 ` Ross Zwisler
2015-10-01 22:32 ` Dave Chinner
2015-10-01 22:47 ` Ross Zwisler
2015-10-01 7:46 ` [PATCH 2/7] Revert "dax: fix race between simultaneous faults" Dave Chinner
2015-10-01 7:46 ` [PATCH 3/7] xfs: fix inode size update overflow in xfs_map_direct() Dave Chinner
2015-10-01 7:46 ` [PATCH 4/7] xfs: introduce BMAPI_ZERO for allocating zeroed extents Dave Chinner
2015-10-01 7:46 ` [PATCH 5/7] xfs: Don't use unwritten extents for DAX Dave Chinner
2015-10-01 7:46 ` [PATCH 6/7] xfs: DAX does not use IO completion callbacks Dave Chinner
2015-10-01 7:46 ` [PATCH 7/7] xfs: add ->pfn_mkwrite support for DAX Dave Chinner
2015-10-01 20:31 ` [PATCH 0/7] xfs, dax: fix the page fault/allocation mess Ross Zwisler
2015-10-01 22:54 ` Dave Chinner
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=201510011627.eAfVmtFF%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=kbuild-all@01.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=willy@linux.intel.com \
--cc=xfs@oss.sgi.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).