From: kbuild test robot <lkp@intel.com>
To: Alexey Lyashkov <alexey.lyashkov@gmail.com>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org,
Andreas Dilger <adilger@dilger.ca>, Jan Kara <jack@suse.cz>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH v2 1/2] Re introduces a DCACHE_DENTRY_UNHASHED flag
Date: Wed, 2 Nov 2016 00:10:14 +0800 [thread overview]
Message-ID: <201611012356.pKzeKr8s%fengguang.wu@intel.com> (raw)
In-Reply-To: <147801241940.67124.14554112464218635024.stgit@alexeys-macbook-pro.local>
[-- Attachment #1: Type: text/plain, Size: 2463 bytes --]
Hi Alexey,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.9-rc3 next-20161028]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Alexey-Lyashkov/d_unhashed-fixes-and-cleanup/20161101-230954
config: powerpc-defconfig (attached as .config)
compiler: powerpc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=powerpc
All errors (new ones prefixed by >>):
arch/powerpc/platforms/cell/spufs/inode.c: In function 'spufs_prune_dir':
>> arch/powerpc/platforms/cell/spufs/inode.c:171:4: error: implicit declaration of function '__d_drop' [-Werror=implicit-function-declaration]
__d_drop(dentry);
^~~~~~~~
cc1: some warnings being treated as errors
vim +/__d_drop +171 arch/powerpc/platforms/cell/spufs/inode.c
6263203ed Arnd Bergmann 2006-10-04 165
5955102c9 Al Viro 2016-01-22 166 inode_lock(d_inode(dir));
946e51f2b Al Viro 2014-10-26 167 list_for_each_entry_safe(dentry, tmp, &dir->d_subdirs, d_child) {
67207b966 Arnd Bergmann 2005-11-15 168 spin_lock(&dentry->d_lock);
dc3f4198e Al Viro 2015-05-18 169 if (simple_positive(dentry)) {
dc0474be3 Nick Piggin 2011-01-07 170 dget_dlock(dentry);
67207b966 Arnd Bergmann 2005-11-15 @171 __d_drop(dentry);
67207b966 Arnd Bergmann 2005-11-15 172 spin_unlock(&dentry->d_lock);
75c3cfa85 David Howells 2015-03-17 173 simple_unlink(d_inode(dir), dentry);
b5c84bf6f Nick Piggin 2011-01-07 174 /* XXX: what was dcache_lock protecting here? Other
:::::: The code at line 171 was first introduced by commit
:::::: 67207b9664a8d603138ef1556141e6d0a102bea7 [PATCH] spufs: The SPU file system, base
:::::: TO: Arnd Bergmann <arnd@arndb.de>
:::::: CC: Paul Mackerras <paulus@samba.org>
---
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: 22609 bytes --]
next prev parent reply other threads:[~2016-11-01 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 15:00 [PATCH v2 0/2] d_unhashed fixes and cleanup Alexey Lyashkov
2016-11-01 15:00 ` [PATCH v2 1/2] Re introduces a DCACHE_DENTRY_UNHASHED flag Alexey Lyashkov
2016-11-01 15:35 ` kbuild test robot
2016-11-01 16:10 ` kbuild test robot [this message]
2016-11-01 15:01 ` [PATCH v2 2/2] cleanup of d_unhashed usage Alexey Lyashkov
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=201611012356.pKzeKr8s%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=adilger@dilger.ca \
--cc=alexey.lyashkov@gmail.com \
--cc=jack@suse.cz \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).