From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [djwong-xfs:scrub-drain-intents 330/330] fs/xfs/xfs_mount.c:1579:22: error: no member named 'm_rt_intents' in 'struct xfs_mount'
Date: Sat, 01 May 2021 20:05:20 +0800 [thread overview]
Message-ID: <202105012009.g2lA2Mut-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 6357 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git scrub-drain-intents
head: ff189938bfb5f2e53a131069b2f4b0b4e311c949
commit: ff189938bfb5f2e53a131069b2f4b0b4e311c949 [330/330] xfs: allow queued AG intents to drain before scrubbing
config: x86_64-randconfig-a016-20210430 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 8f5a2a5836cc8e4c1def2bdeb022e7b496623439)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?id=ff189938bfb5f2e53a131069b2f4b0b4e311c949
git remote add djwong-xfs https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git
git fetch --no-tags djwong-xfs scrub-drain-intents
git checkout ff189938bfb5f2e53a131069b2f4b0b4e311c949
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> fs/xfs/xfs_mount.c:1579:22: error: no member named 'm_rt_intents' in 'struct xfs_mount'
atomic_read(&mp->m_rt_intents), _RET_IP_);
~~ ^
fs/xfs/xfs_mount.c:1580:19: error: no member named 'm_rt_intents' in 'struct xfs_mount'
atomic_inc(&mp->m_rt_intents);
~~ ^
fs/xfs/xfs_mount.c:1604:27: error: no member named 'm_rt_intents' in 'struct xfs_mount'
ASSERT(atomic_read(&mp->m_rt_intents) > 0);
~~ ^
fs/xfs/xfs_linux.h:212:10: note: expanded from macro 'ASSERT'
(likely(expr) ? (void)0 : asswarn(NULL, #expr, __FILE__, __LINE__))
^~~~
include/linux/compiler.h:45:39: note: expanded from macro 'likely'
# define likely(x) (__branch_check__(x, 1, __builtin_constant_p(x)))
^
include/linux/compiler.h:33:34: note: expanded from macro '__branch_check__'
______r = __builtin_expect(!!(x), expect); \
^
fs/xfs/xfs_mount.c:1604:27: error: no member named 'm_rt_intents' in 'struct xfs_mount'
ASSERT(atomic_read(&mp->m_rt_intents) > 0);
~~ ^
fs/xfs/xfs_linux.h:212:10: note: expanded from macro 'ASSERT'
(likely(expr) ? (void)0 : asswarn(NULL, #expr, __FILE__, __LINE__))
^~~~
include/linux/compiler.h:45:66: note: expanded from macro 'likely'
# define likely(x) (__branch_check__(x, 1, __builtin_constant_p(x)))
^
include/linux/compiler.h:35:19: note: expanded from macro '__branch_check__'
expect, is_constant); \
^~~~~~~~~~~
fs/xfs/xfs_mount.c:1606:22: error: no member named 'm_rt_intents' in 'struct xfs_mount'
atomic_read(&mp->m_rt_intents), _RET_IP_);
~~ ^
fs/xfs/xfs_mount.c:1607:32: error: no member named 'm_rt_intents' in 'struct xfs_mount'
if (atomic_dec_and_test(&mp->m_rt_intents))
~~ ^
>> fs/xfs/xfs_mount.c:1608:17: error: no member named 'm_rt_intents_wq' in 'struct xfs_mount'
wake_up(&mp->m_rt_intents_wq);
~~ ^
include/linux/wait.h:221:32: note: expanded from macro 'wake_up'
#define wake_up(x) __wake_up(x, TASK_NORMAL, 1, NULL)
^
7 errors generated.
--
>> fs/xfs/scrub/common.c:736:35: error: no member named 'm_rt_intents' in 'struct xfs_mount'
int intents = atomic_read(&mp->m_rt_intents);
~~ ^
1 error generated.
vim +1579 fs/xfs/xfs_mount.c
1566
1567 #if IS_ENABLED(CONFIG_XFS_ONLINE_SCRUB)
1568 void
1569 xfs_fs_bump_intents(
1570 struct xfs_mount *mp,
1571 bool is_rt,
1572 xfs_fsblock_t fsbno)
1573 {
1574 xfs_agnumber_t agno;
1575 struct xfs_perag *pag;
1576
1577 if (is_rt) {
1578 trace_xfs_fs_bump_intents(mp, -1U,
> 1579 atomic_read(&mp->m_rt_intents), _RET_IP_);
1580 atomic_inc(&mp->m_rt_intents);
1581 return;
1582 }
1583
1584 agno = XFS_FSB_TO_AGNO(mp, fsbno);
1585 pag = xfs_perag_get(mp, agno);
1586
1587 trace_xfs_fs_bump_intents(mp, agno, atomic_read(&pag->pag_intents),
1588 _RET_IP_);
1589
1590 atomic_inc(&pag->pag_intents);
1591 xfs_perag_put(pag);
1592 }
1593
1594 void
1595 xfs_fs_drop_intents(
1596 struct xfs_mount *mp,
1597 bool is_rt,
1598 xfs_fsblock_t fsbno)
1599 {
1600 xfs_agnumber_t agno;
1601 struct xfs_perag *pag;
1602
1603 if (is_rt) {
1604 ASSERT(atomic_read(&mp->m_rt_intents) > 0);
1605 trace_xfs_fs_drop_intents(mp, -1U,
1606 atomic_read(&mp->m_rt_intents), _RET_IP_);
1607 if (atomic_dec_and_test(&mp->m_rt_intents))
> 1608 wake_up(&mp->m_rt_intents_wq);
1609 return;
1610 }
1611
1612 agno = XFS_FSB_TO_AGNO(mp, fsbno);
1613 pag = xfs_perag_get(mp, agno);
1614
1615 ASSERT(atomic_read(&pag->pag_intents) > 0);
1616 trace_xfs_fs_drop_intents(mp, agno, atomic_read(&pag->pag_intents),
1617 _RET_IP_);
1618
1619 if (atomic_dec_and_test(&pag->pag_intents))
1620 wake_up(&pag->pag_intents_wq);
1621 xfs_perag_put(pag);
1622 }
1623
---
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: 39645 bytes --]
reply other threads:[~2021-05-01 12:05 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=202105012009.g2lA2Mut-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.