From: kbuild test robot <lkp@intel.com>
To: Chris Mason <chris.mason@fusionio.com>
Cc: kbuild-all@01.org, linux-btrfs@vger.kernel.org
Subject: [btrfs:for-kdave 7/8] ERROR: "wbc_detach_inode" [fs/btrfs/btrfs.ko] undefined!
Date: Tue, 7 May 2019 05:26:50 +0800 [thread overview]
Message-ID: <201905070548.4PDtfcLE%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-kdave
head: 6eb23136f1d35452008e6a442e152cf89e2f1d4b
commit: 92be453deb4ea50e01f2cf26157d11e34f34db5b [7/8] btrfs: extent_write_locked_range() should attach inode->i_wb
config: x86_64-kexec (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout 92be453deb4ea50e01f2cf26157d11e34f34db5b
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> ERROR: "__inode_attach_wb" [fs/btrfs/btrfs.ko] undefined!
>> ERROR: "wbc_attach_and_unlock_inode" [fs/btrfs/btrfs.ko] undefined!
>> ERROR: "wbc_detach_inode" [fs/btrfs/btrfs.ko] undefined!
---
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: 26469 bytes --]
reply other threads:[~2019-05-06 21:27 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=201905070548.4PDtfcLE%lkp@intel.com \
--to=lkp@intel.com \
--cc=chris.mason@fusionio.com \
--cc=kbuild-all@01.org \
--cc=linux-btrfs@vger.kernel.org \
/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).