From: kbuild test robot <fengguang.wu@intel.com>
To: Eric Ren <zren@suse.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 26/204] fs/ocfs2/dlmglue.h:189:29: error: inlining failed in call to always_inline 'ocfs2_is_locked_by_me': function body not available
Date: Sun, 15 Jan 2017 11:45:45 +0800 [thread overview]
Message-ID: <201701151142.n318fVY1%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5759 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: d96a8a235309d25e8aad738bda343d6196ab4542
commit: d52139c08f82d26028b2659c4a5ae91f6ea47956 [26/204] ocfs2: fix deadlocks when taking inode lock at vfs entry points
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-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
git checkout d52139c08f82d26028b2659c4a5ae91f6ea47956
# save the attached .config to linux build tree
make.cross ARCH=arm
All errors (new ones prefixed by >>):
In file included from fs/ocfs2/file.c:49:0:
fs/ocfs2/file.c: In function 'ocfs2_permission':
>> fs/ocfs2/dlmglue.h:189:29: error: inlining failed in call to always_inline 'ocfs2_is_locked_by_me': function body not available
inline struct ocfs2_holder *ocfs2_is_locked_by_me(struct ocfs2_lock_res *lockres);
^~~~~~~~~~~~~~~~~~~~~
fs/ocfs2/file.c:1345:16: note: called from here
has_locked = (ocfs2_is_locked_by_me(lockres) != NULL);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from fs/ocfs2/file.c:49:0:
>> fs/ocfs2/dlmglue.h:189:29: error: inlining failed in call to always_inline 'ocfs2_is_locked_by_me': function body not available
inline struct ocfs2_holder *ocfs2_is_locked_by_me(struct ocfs2_lock_res *lockres);
^~~~~~~~~~~~~~~~~~~~~
fs/ocfs2/file.c:1345:16: note: called from here
has_locked = (ocfs2_is_locked_by_me(lockres) != NULL);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from fs/ocfs2/file.c:49:0:
>> fs/ocfs2/dlmglue.h:185:13: error: inlining failed in call to always_inline 'ocfs2_add_holder': function body not available
inline void ocfs2_add_holder(struct ocfs2_lock_res *lockres,
^~~~~~~~~~~~~~~~
fs/ocfs2/file.c:1353:3: note: called from here
ocfs2_add_holder(lockres, &oh);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from fs/ocfs2/file.c:49:0:
>> fs/ocfs2/dlmglue.h:187:13: error: inlining failed in call to always_inline 'ocfs2_remove_holder': function body not available
inline void ocfs2_remove_holder(struct ocfs2_lock_res *lockres,
^~~~~~~~~~~~~~~~~~~
fs/ocfs2/file.c:1359:3: note: called from here
ocfs2_remove_holder(lockres, &oh);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
In file included from fs/ocfs2/acl.c:31:0:
fs/ocfs2/acl.c: In function 'ocfs2_iop_set_acl':
>> fs/ocfs2/dlmglue.h:189:29: error: inlining failed in call to always_inline 'ocfs2_is_locked_by_me': function body not available
inline struct ocfs2_holder *ocfs2_is_locked_by_me(struct ocfs2_lock_res *lockres);
^~~~~~~~~~~~~~~~~~~~~
fs/ocfs2/acl.c:292:16: note: called from here
has_locked = (ocfs2_is_locked_by_me(lockres) != NULL);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from fs/ocfs2/acl.c:31:0:
>> fs/ocfs2/dlmglue.h:189:29: error: inlining failed in call to always_inline 'ocfs2_is_locked_by_me': function body not available
inline struct ocfs2_holder *ocfs2_is_locked_by_me(struct ocfs2_lock_res *lockres);
^~~~~~~~~~~~~~~~~~~~~
fs/ocfs2/acl.c:292:16: note: called from here
has_locked = (ocfs2_is_locked_by_me(lockres) != NULL);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from fs/ocfs2/acl.c:31:0:
>> fs/ocfs2/dlmglue.h:185:13: error: inlining failed in call to always_inline 'ocfs2_add_holder': function body not available
inline void ocfs2_add_holder(struct ocfs2_lock_res *lockres,
^~~~~~~~~~~~~~~~
fs/ocfs2/acl.c:302:3: note: called from here
ocfs2_add_holder(lockres, &oh);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from fs/ocfs2/acl.c:31:0:
>> fs/ocfs2/dlmglue.h:187:13: error: inlining failed in call to always_inline 'ocfs2_remove_holder': function body not available
inline void ocfs2_remove_holder(struct ocfs2_lock_res *lockres,
^~~~~~~~~~~~~~~~~~~
fs/ocfs2/acl.c:307:3: note: called from here
ocfs2_remove_holder(lockres, &oh);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/ocfs2_is_locked_by_me +189 fs/ocfs2/dlmglue.h
63e0c48a Joel Becker 2008-01-30 179 void ocfs2_set_locking_protocol(void);
242359b9 Eric Ren 2017-01-12 180
242359b9 Eric Ren 2017-01-12 181 /*
242359b9 Eric Ren 2017-01-12 182 * Keep a list of processes who have interest in a lockres.
242359b9 Eric Ren 2017-01-12 183 * Note: this is now only uesed for check recursive cluster lock.
242359b9 Eric Ren 2017-01-12 184 */
242359b9 Eric Ren 2017-01-12 @185 inline void ocfs2_add_holder(struct ocfs2_lock_res *lockres,
242359b9 Eric Ren 2017-01-12 186 struct ocfs2_holder *oh);
242359b9 Eric Ren 2017-01-12 @187 inline void ocfs2_remove_holder(struct ocfs2_lock_res *lockres,
242359b9 Eric Ren 2017-01-12 188 struct ocfs2_holder *oh);
242359b9 Eric Ren 2017-01-12 @189 inline struct ocfs2_holder *ocfs2_is_locked_by_me(struct ocfs2_lock_res *lockres);
242359b9 Eric Ren 2017-01-12 190
ccd979bd Mark Fasheh 2005-12-15 191 #endif /* DLMGLUE_H */
:::::: The code at line 189 was first introduced by commit
:::::: 242359b9dabc564809bcc0a31cc697e26304abe2 ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock
:::::: TO: Eric Ren <zren@suse.com>
:::::: CC: Johannes Weiner <hannes@cmpxchg.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: 60371 bytes --]
reply other threads:[~2017-01-15 3:38 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=201701151142.n318fVY1%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=zren@suse.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