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-5.10 3401/3401] fs/xfs/libxfs/xfs_alloc.c:91:1: warning: no previous prototype for 'xfs_ag_fixup_aside'
Date: Thu, 11 Dec 2025 05:14:17 +0800 [thread overview]
Message-ID: <202512110538.DUkYagUT-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-5.10
head: 41baca24098d5757f3aea4d98e63eb9d9f7d43a3
commit: 12a5c9f8f69c682f3aaf799a18f4a3631cc9bfbc [3401/3401] xfs: fix xfs shutdown since we reserve more blocks in agfl fixup
config: x86_64-randconfig-161-20251210 (https://download.01.org/0day-ci/archive/20251211/202512110538.DUkYagUT-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.4.0-5) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251211/202512110538.DUkYagUT-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/202512110538.DUkYagUT-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/xfs/libxfs/xfs_alloc.c:91:1: warning: no previous prototype for 'xfs_ag_fixup_aside' [-Wmissing-prototypes]
91 | xfs_ag_fixup_aside(
| ^~~~~~~~~~~~~~~~~~
vim +/xfs_ag_fixup_aside +91 fs/xfs/libxfs/xfs_alloc.c
83
84 /*
85 * Twice fixup for the same ag may happen within exact one tp, and the consume
86 * of agfl after first fixup may trigger second fixup's failure, then xfs will
87 * shutdown. To avoid that, we reserve blocks which can satisfy the second
88 * fixup.
89 */
90 xfs_extlen_t
> 91 xfs_ag_fixup_aside(
92 struct xfs_mount *mp)
93 {
94 xfs_extlen_t ret;
95
96 ret = 2 * mp->m_ag_maxlevels;
97 if (xfs_has_rmapbt(mp))
98 ret += mp->m_rmap_maxlevels;
99
100 return ret;
101 }
102
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-10 21:14 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=202512110538.DUkYagUT-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.