From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [linux-next:master 10338/10705] tools/testing/selftests/kselftest.h:427:13: error: implicit declaration of function 'vasprintf'; did you mean 'vsprintf'?
Date: Fri, 03 Apr 2026 16:44:21 +0800 [thread overview]
Message-ID: <202604030814.5B6AanyA-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Chunyu Hu <chuhu@redhat.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: bd0f139e5fc11182777b81cefc3893ea508544ec
commit: cc0b04b10a7b98fd8df2fd539177e94e0f83a5c3 [10338/10705] selftests: ksft_exit_fail_perror: support printf style arguments
:::::: branch date: 34 hours ago
:::::: commit date: 3 days ago
config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260403/202604030814.5B6AanyA-lkp@intel.com/config)
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260403/202604030814.5B6AanyA-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/r/202604030814.5B6AanyA-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from za-fork.c:12:
../../kselftest.h: In function 'ksft_exit_fail_perror':
>> ../../kselftest.h:427:13: error: implicit declaration of function 'vasprintf'; did you mean 'vsprintf'? [-Wimplicit-function-declaration]
427 | if (vasprintf(&buf, msg, args) == -1) {
| ^~~~~~~~~
| vsprintf
--
In file included from basic-gcs.c:16:
tools/testing/selftests/kselftest.h: In function 'ksft_exit_fail_perror':
>> tools/testing/selftests/kselftest.h:427:13: error: implicit declaration of function 'vasprintf'; did you mean 'vsprintf'? [-Wimplicit-function-declaration]
427 | if (vasprintf(&buf, msg, args) == -1) {
| ^~~~~~~~~
| vsprintf
vim +427 tools/testing/selftests/kselftest.h
b6a4b66d845ae4 Paul Elder 2017-06-12 419
cc0b04b10a7b98 Chunyu Hu 2026-03-30 420 static inline __noreturn __printf(1, 2) void ksft_exit_fail_perror(const char *msg, ...)
86483f8b4e8d3e Muhammad Usama Anjum 2024-04-04 421 {
cc0b04b10a7b98 Chunyu Hu 2026-03-30 422 va_list args;
cc0b04b10a7b98 Chunyu Hu 2026-03-30 423 char *buf = NULL;
cc0b04b10a7b98 Chunyu Hu 2026-03-30 424 int saved_errno = errno;
cc0b04b10a7b98 Chunyu Hu 2026-03-30 425
cc0b04b10a7b98 Chunyu Hu 2026-03-30 426 va_start(args, msg);
cc0b04b10a7b98 Chunyu Hu 2026-03-30 @427 if (vasprintf(&buf, msg, args) == -1) {
cc0b04b10a7b98 Chunyu Hu 2026-03-30 428 va_end(args);
cc0b04b10a7b98 Chunyu Hu 2026-03-30 429 ksft_exit_fail_msg("vasprintf failed: %s (%d)\n", strerror(saved_errno),
cc0b04b10a7b98 Chunyu Hu 2026-03-30 430 saved_errno);
cc0b04b10a7b98 Chunyu Hu 2026-03-30 431 }
cc0b04b10a7b98 Chunyu Hu 2026-03-30 432 va_end(args);
cc0b04b10a7b98 Chunyu Hu 2026-03-30 433
cc0b04b10a7b98 Chunyu Hu 2026-03-30 434 errno = saved_errno;
cc0b04b10a7b98 Chunyu Hu 2026-03-30 435 ksft_exit_fail_msg("%s: %s (%d)\n", buf, strerror(errno), errno);
cc0b04b10a7b98 Chunyu Hu 2026-03-30 436
cc0b04b10a7b98 Chunyu Hu 2026-03-30 437 free(buf);
86483f8b4e8d3e Muhammad Usama Anjum 2024-04-04 438 }
86483f8b4e8d3e Muhammad Usama Anjum 2024-04-04 439
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-03 8:44 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=202604030814.5B6AanyA-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox