From: kbuild test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: kbuild-all@01.org, viro@zeniv.linux.org.uk,
linux-nfs@vger.kernel.org, Jeff Layton <jlayton@redhat.com>,
linux-kernel@vger.kernel.org, Jianhong Yin <jiyin@redhat.com>,
Steve Dickson <steved@redhat.com>,
dhowells@redhat.com, linux-cachefs@redhat.com,
stable@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] cachefiles: Fix attempt to read i_blocks after deleting file
Date: Tue, 9 Aug 2016 21:16:49 +0800 [thread overview]
Message-ID: <201608092153.DwcixKJC%fengguang.wu@intel.com> (raw)
In-Reply-To: <147074698645.18102.17742162122820513623.stgit@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
Hi David,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.8-rc1 next-20160809]
[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/David-Howells/cachefiles-Fix-attempt-to-read-i_blocks-after-deleting-file/20160809-205541
config: i386-randconfig-s0-201632 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
fs/cachefiles/namei.c: In function 'cachefiles_mark_object_inactive':
>> fs/cachefiles/namei.c:269:2: error: implicit declaration of function 'trace_cachefiles_mark_inactive' [-Werror=implicit-function-declaration]
trace_cachefiles_mark_inactive(object, dentry,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/trace_cachefiles_mark_inactive +269 fs/cachefiles/namei.c
263 void cachefiles_mark_object_inactive(struct cachefiles_cache *cache,
264 struct cachefiles_object *object,
265 blkcnt_t i_blocks)
266 {
267 struct dentry *dentry = object->dentry;
268
> 269 trace_cachefiles_mark_inactive(object, dentry,
270 d_backing_inode(dentry));
271
272 write_lock(&cache->active_lock);
---
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: 34099 bytes --]
prev parent reply other threads:[~2016-08-09 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 12:49 [PATCH] cachefiles: Fix attempt to read i_blocks after deleting file David Howells
2016-08-09 13:16 ` kbuild test robot [this message]
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=201608092153.DwcixKJC%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=jiyin@redhat.com \
--cc=jlayton@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=steved@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.