From: kbuild test robot <lkp@intel.com>
To: sunqiuyang <sunqiuyang@huawei.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, sunqiuyang@huawei.com
Subject: Re: [PATCH v3] f2fs: dax: implement direct access
Date: Thu, 8 Jun 2017 14:37:32 +0800 [thread overview]
Message-ID: <201706081400.lVtm8m79%fengguang.wu@intel.com> (raw)
In-Reply-To: <1496827763-575-1-git-send-email-sunqiuyang@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2477 bytes --]
Hi Qiuyang,
[auto build test ERROR on f2fs/dev]
[also build test ERROR on v4.12-rc4 next-20170607]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/sunqiuyang/f2fs-dax-implement-direct-access/20170608-140734
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev
config: x86_64-randconfig-x010-201723 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
fs/f2fs/file.c: In function 'f2fs_dax_huge_fault':
>> fs/f2fs/file.c:124:26: error: 'struct f2fs_inode_info' has no member named 'i_mmap_sem'; did you mean 'i_sem'?
down_read(&F2FS_I(inode)->i_mmap_sem);
^~
fs/f2fs/file.c:126:24: error: 'struct f2fs_inode_info' has no member named 'i_mmap_sem'; did you mean 'i_sem'?
up_read(&F2FS_I(inode)->i_mmap_sem);
^~
fs/f2fs/file.c: In function 'f2fs_dax_pfn_mkwrite':
fs/f2fs/file.c:147:26: error: 'struct f2fs_inode_info' has no member named 'i_mmap_sem'; did you mean 'i_sem'?
down_read(&F2FS_I(inode)->i_mmap_sem);
^~
fs/f2fs/file.c:153:24: error: 'struct f2fs_inode_info' has no member named 'i_mmap_sem'; did you mean 'i_sem'?
up_read(&F2FS_I(inode)->i_mmap_sem);
^~
--
fs/f2fs/gc.c: In function 'dax_move_data_page':
>> fs/f2fs/gc.c:731:40: error: 'struct f2fs_inode_info' has no member named 'i_mmap_sem'; did you mean 'i_sem'?
if (!down_write_trylock(&F2FS_I(inode)->i_mmap_sem))
^~
fs/f2fs/gc.c:783:25: error: 'struct f2fs_inode_info' has no member named 'i_mmap_sem'; did you mean 'i_sem'?
up_write(&F2FS_I(inode)->i_mmap_sem);
^~
vim +124 fs/f2fs/file.c
118 bool write = vmf->flags & FAULT_FLAG_WRITE;
119
120 if (write) {
121 sb_start_pagefault(sb);
122 file_update_time(vmf->vma->vm_file);
123 }
> 124 down_read(&F2FS_I(inode)->i_mmap_sem);
125 result = dax_iomap_fault(vmf, pe_size, &f2fs_iomap_ops);
126 up_read(&F2FS_I(inode)->i_mmap_sem);
127 if (write)
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 25418 bytes --]
next prev parent reply other threads:[~2017-06-08 6:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 9:29 sunqiuyang
2017-06-07 15:42 ` [f2fs-dev] " Chao Yu
2017-06-08 9:38 ` Sun Qiuyang
2017-06-08 10:59 ` Chao Yu
2017-06-08 6:37 ` kbuild test robot [this message]
2017-06-08 7:35 ` kbuild test robot
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=201706081400.lVtm8m79%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunqiuyang@huawei.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
all inboxes | Powered by JetHome®