The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Wang Yibo <wangyibo@kylinos.cn>, arlos Maiolino <cem@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: convert the dahash test to KUnit
Date: Fri, 13 Nov 2026 03:17:39 +0800	[thread overview]
Message-ID: <202611130302.dGXAb4Py-lkp@intel.com> (raw)
In-Reply-To: <20261112041631.2792545-1-wangyibo@kylinos.cn>

Hi Wang,

kernel test robot noticed the following build errors:

[auto build test ERROR on xfs-linux/for-next]
[also build test ERROR on linus/master v7.4-rc2 next-20261111]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Wang-Yibo/xfs-convert-the-dahash-test-to-KUnit/20261112-121631
base:   https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git for-next
patch link:    https://lore.kernel.org/r/20261112041631.2792545-1-wangyibo%40kylinos.cn
patch subject: [PATCH] xfs: convert the dahash test to KUnit
config: i386-randconfig-1012-20261112 (https://download.01.org/0day-ci/archive/20261113/202611130302.dGXAb4Py-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261113/202611130302.dGXAb4Py-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/202611130302.dGXAb4Py-lkp@intel.com/

All errors (new ones prefixed by >>):

   ld: fs/xfs/xfs_dahash_test.o: in function `xfs_ascii_ci_hashname_case':
>> fs/xfs/xfs_dahash_test.c:671:(.text+0x88): undefined reference to `kunit_binary_assert_format'
>> ld: fs/xfs/xfs_dahash_test.c:671:(.text+0xc0): undefined reference to `__kunit_do_failed_assertion'
   ld: fs/xfs/xfs_dahash_test.o: in function `xfs_da_hashname_case':
   fs/xfs/xfs_dahash_test.c:655:(.text+0x178): undefined reference to `kunit_binary_assert_format'
   ld: fs/xfs/xfs_dahash_test.c:655:(.text+0x1b0): undefined reference to `__kunit_do_failed_assertion'


vim +671 fs/xfs/xfs_dahash_test.c

   658	
   659	static void xfs_ascii_ci_hashname_case(struct kunit *test)
   660	{
   661		unsigned int	i;
   662	
   663		for (i = 0; i < ARRAY_SIZE(dahash_test_vecs); i++) {
   664			const struct dahash_test	*tv = &dahash_test_vecs[i];
   665			struct xfs_name			xname = { };
   666			xfs_dahash_t			hash;
   667	
   668			xname.name = test_buf + tv->start;
   669			xname.len = tv->length;
   670			hash = xfs_ascii_ci_hashname(&xname);
 > 671			KUNIT_EXPECT_EQ_MSG(test, hash, tv->ascii_ci_dahash,
   672					    "case %u", i);
   673		}
   674	}
   675	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      reply	other threads:[~2026-11-12 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12  4:16 [PATCH] xfs: convert the dahash test to KUnit Wang Yibo
2026-11-12 19:17 ` kernel test robot [this message]

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=202611130302.dGXAb4Py-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cem@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=wangyibo@kylinos.cn \
    /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