From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [dgc-xfs:xfs-async-inode-reclaim-2 12/32] fs/xfs/xfs_buf_item.c:1228: undefined reference to `xfs_dquot_done'
Date: Tue, 02 Jun 2020 11:00:09 +0800 [thread overview]
Message-ID: <202006021107.T0YEcrxn%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git xfs-async-inode-reclaim-2
head: 87065b70f597fd208e30f2772cfb680591726811
commit: 246e0164336066ee540d5174ae181daaa8891670 [12/32] xfs: use direct calls for dquot IO completion
config: i386-randconfig-c001-20200602 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
ld: fs/xfs/xfs_buf_item.o: in function `xfs_buf_dquot_iodone':
>> fs/xfs/xfs_buf_item.c:1228: undefined reference to `xfs_dquot_done'
vim +1228 fs/xfs/xfs_buf_item.c
1207
1208 /*
1209 * Dquot buffer iodone callback function.
1210 */
1211 void
1212 xfs_buf_dquot_iodone(
1213 struct xfs_buf *bp)
1214 {
1215 struct xfs_buf_log_item *blip = bp->b_log_item;
1216 struct xfs_log_item *lip;
1217
1218 if (xfs_buf_had_callback_errors(bp))
1219 return;
1220
1221 /* a newly allocated dquot buffer might have a log item attached */
1222 if (blip) {
1223 lip = &blip->bli_item;
1224 lip->li_cb(bp, lip);
1225 bp->b_log_item = NULL;
1226 }
1227
> 1228 xfs_dquot_done(bp);
1229 xfs_buf_ioend_finish(bp);
1230 }
1231
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 32246 bytes --]
reply other threads:[~2020-06-02 3:00 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=202006021107.T0YEcrxn%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.