From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Roman Gushchin <roman.gushchin@linux.dev>,
Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: mm/slub.c:3330:28: error: implicit declaration of function 'node_nr_objs'; did you mean 'node_nr_slabs'?
Date: Tue, 23 Apr 2024 13:53:30 +0530 [thread overview]
Message-ID: <CA+G9fYuu0SApq057AMQmOiUC1upt_akKYfhu4BR+2BDkMoqs=w@mail.gmail.com> (raw)
The arm and mips builds failed due to following warnings / errors with
gcc-13 / gcc-12 and clang-17 on the Linux next-20240423 tag.
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
arm:
- imx_v6_v7_defconfig
- orion5x_defconfig
mips:
- defconfig
- ath79_defconfig
- bcm63xx_defconfig
In file included from include/linux/export.h:5,
from include/linux/linkage.h:7,
from arch/arm/include/asm/bug.h:5,
from include/linux/bug.h:5,
from include/linux/mmdebug.h:5,
from include/linux/mm.h:6,
from mm/slub.c:13:
mm/slub.c: In function 'count_partial_free_approx':
mm/slub.c:3330:28: error: implicit declaration of function
'node_nr_objs'; did you mean 'node_nr_slabs'?
[-Werror=implicit-function-declaration]
3330 | x = min(x, node_nr_objs(n));
| ^~~~~~~~~~~~
include/linux/compiler.h:286:55: note: in definition of macro '__is_constexpr'
286 | (sizeof(int) == sizeof(*(8 ? ((void *)((long)(x) *
0l)) : (int *)8)))
| ^
include/linux/minmax.h:85:25: note: in expansion of macro '__careful_cmp'
85 | #define min(x, y) __careful_cmp(min, x, y)
| ^~~~~~~~~~~~~
mm/slub.c:3330:21: note: in expansion of macro 'min'
3330 | x = min(x, node_nr_objs(n));
| ^~~
In file included from include/linux/init.h:5,
from include/linux/printk.h:6,
from include/asm-generic/bug.h:22,
from arch/arm/include/asm/bug.h:60:
include/linux/build_bug.h:78:41: error: static assertion failed:
"min(x, node_nr_objs(n)) signedness error, fix types or consider
umin() before min_t()"
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
| ^~~~~~~~~~~~~~
include/linux/build_bug.h:77:34: note: in expansion of macro '__static_assert'
77 | #define static_assert(expr, ...) __static_assert(expr,
##__VA_ARGS__, #expr)
| ^~~~~~~~~~~~~~~
include/linux/minmax.h:51:9: note: in expansion of macro 'static_assert'
51 | static_assert(__types_ok(x, y), \
| ^~~~~~~~~~~~~
include/linux/minmax.h:58:17: note: in expansion of macro '__cmp_once'
58 | __cmp_once(op, x, y, __UNIQUE_ID(__x),
__UNIQUE_ID(__y)))
| ^~~~~~~~~~
include/linux/minmax.h:85:25: note: in expansion of macro '__careful_cmp'
85 | #define min(x, y) __careful_cmp(min, x, y)
| ^~~~~~~~~~~~~
mm/slub.c:3330:21: note: in expansion of macro 'min'
3330 | x = min(x, node_nr_objs(n));
| ^~~
mm/slub.c: At top level:
mm/slub.c:3301:22: warning: 'count_partial_free_approx' defined but
not used [-Wunused-function]
3301 | static unsigned long count_partial_free_approx(struct
kmem_cache_node *n)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
Steps to reproduce:
---
# tuxmake --runtime podman --target-arch arm --toolchain gcc-13
--kconfig orion5x_defconfig
Links:
- https://storage.tuxsuite.com/public/linaro/lkft/builds/2fUaQMPe7cZ5qJJOt50avspw7bH/
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240423/testrun/23561861/suite/build/test/gcc-13-orion5x_defconfig/details/
--
Linaro LKFT
https://lkft.linaro.org
reply other threads:[~2024-04-23 8:23 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='CA+G9fYuu0SApq057AMQmOiUC1upt_akKYfhu4BR+2BDkMoqs=w@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=regressions@lists.linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).