From: kbuild test robot <fengguang.wu@intel.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 9533/9538] fs/dax.c:916:17: warning: passing argument 1 of '__dax_dbg' from incompatible pointer type
Date: Fri, 1 Jan 2016 01:20:30 +0800 [thread overview]
Message-ID: <201601010127.qDNlPp5A%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 719d6c1b9f86112fd9b5771ff009f678c1e00845
commit: 3cb108f941debe7449cb5de6e9898822d341a49c [9533/9538] dax-add-support-for-fsync-sync-v6
config: x86_64-randconfig-s2-01010040 (attached as .config)
reproduce:
git checkout 3cb108f941debe7449cb5de6e9898822d341a49c
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
fs/dax.c: In function '__dax_pmd_fault':
>> fs/dax.c:916:17: warning: passing argument 1 of '__dax_dbg' from incompatible pointer type [-Wincompatible-pointer-types]
dax_pmd_dbg(bdev, address,
^
fs/dax.c:754:52: note: in definition of macro 'dax_pmd_dbg'
#define dax_pmd_dbg(bh, address, reason) __dax_dbg(bh, address, reason, "dax_pmd")
^
fs/dax.c:738:13: note: expected 'struct buffer_head *' but argument is of type 'struct block_device *'
static void __dax_dbg(struct buffer_head *bh, unsigned long address,
^
vim +/__dax_dbg +916 fs/dax.c
900 goto fallback;
901 }
902
903 if (buffer_unwritten(&bh) || buffer_new(&bh)) {
904 clear_pmem(dax.addr, PMD_SIZE);
905 wmb_pmem();
906 count_vm_event(PGMAJFAULT);
907 mem_cgroup_count_vm_event(vma->vm_mm, PGMAJFAULT);
908 result |= VM_FAULT_MAJOR;
909 }
910 dax_unmap_atomic(bdev, &dax);
911
912 if (write) {
913 error = dax_radix_entry(mapping, pgoff, dax.sector,
914 true, true);
915 if (error) {
> 916 dax_pmd_dbg(bdev, address,
917 "PMD radix insertion failed");
918 goto fallback;
919 }
920 }
921
922 dev_dbg(part_to_dev(bdev->bd_part),
923 "%s: %s addr: %lx pfn: %lx sect: %llx\n",
924 __func__, current->comm, address,
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 21358 bytes --]
reply other threads:[~2015-12-31 17:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201601010127.qDNlPp5A%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--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).