From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Long Li <leo.lilong@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 1474/1474] fs/xfs/libxfs/xfs_alloc.c:102:1: sparse: sparse: symbol 'xfs_ag_fixup_aside' was not declared. Should it be static?
Date: Mon, 2 Dec 2024 03:51:38 +0800 [thread overview]
Message-ID: <202412020323.jAdcem7b-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: df4c334beecb4cf58e4e8d63b491aa5ac0a84f46
commit: 8c6e9756375dff2e96d3b598992b2f0e8b3682ee [1474/1474] xfs: fix xfs shutdown since we reserve more blocks in agfl fixup
config: x86_64-randconfig-121-20241118 (https://download.01.org/0day-ci/archive/20241202/202412020323.jAdcem7b-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241202/202412020323.jAdcem7b-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202412020323.jAdcem7b-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/xfs/libxfs/xfs_alloc.c:102:1: sparse: sparse: symbol 'xfs_ag_fixup_aside' was not declared. Should it be static?
vim +/xfs_ag_fixup_aside +102 fs/xfs/libxfs/xfs_alloc.c
94
95 /*
96 * Twice fixup for the same ag may happen within exact one tp, and the consume
97 * of agfl after first fixup may trigger second fixup's failure, then xfs will
98 * shutdown. To avoid that, we reserve blocks which can satisfy the second
99 * fixup.
100 */
101 xfs_extlen_t
> 102 xfs_ag_fixup_aside(
103 struct xfs_mount *mp)
104 {
105 xfs_extlen_t ret;
106
107 ret = 2 * mp->m_alloc_maxlevels;
108 if (xfs_has_rmapbt(mp))
109 ret += mp->m_rmap_maxlevels;
110
111 return ret;
112 }
113
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-12-01 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 19:51 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-19 6:46 [openeuler:OLK-6.6 1474/1474] fs/xfs/libxfs/xfs_alloc.c:102:1: sparse: sparse: symbol 'xfs_ag_fixup_aside' was not declared. Should it be static? kernel test robot
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=202412020323.jAdcem7b-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=leo.lilong@huawei.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.