[PATCH v5 6/6] kasan: Forbid kunit tests when async mode is enabled

[kernel test robot]

Hi Vincenzo,

I love your patch! Yet something to improve:

[auto build test ERROR on next-20210121]
[cannot apply to arm64/for-next/core arm/for-next soc/for-next xlnx/master kvmarm/next linus/master hnaz-linux-mm/master v5.11-rc4 v5.11-rc3 v5.11-rc2 v5.11-rc4]
[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]

url:    https://github.com/0day-ci/linux/commits/Vincenzo-Frascino/arm64-ARMv8-5-A-MTE-Add-async-mode-support/20210122-004631
base:    bc085f8fc88fc16796c9f2364e2bfb3fef305cad
config: riscv-randconfig-r003-20210122 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project bd3a387ee76f58caa0d7901f3f84e9bb3d006f27)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install riscv cross compiling tool for clang build
        # apt-get install binutils-riscv64-linux-gnu
        # https://github.com/0day-ci/linux/commit/0ac23ec8a70b5fd68efdec0a6a501bdccddf4d5e
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Vincenzo-Frascino/arm64-ARMv8-5-A-MTE-Add-async-mode-support/20210122-004631
        git checkout 0ac23ec8a70b5fd68efdec0a6a501bdccddf4d5e
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=riscv 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp at intel.com>

All errors (new ones prefixed by >>):

>> lib/test_kasan.c:55:24: error: expected expression
           if (!hw_is_mode_sync()) {
                                 ^
   1 error generated.


vim +55 lib/test_kasan.c

    41	
    42	/*
    43	 * Temporarily enable multi-shot mode. Otherwise, KASAN would only report the
    44	 * first detected bug and panic the kernel if panic_on_warn is enabled. For
    45	 * hardware tag-based KASAN also allow tag checking to be reenabled for each
    46	 * test, see the comment for KUNIT_EXPECT_KASAN_FAIL().
    47	 */
    48	static int kasan_test_init(struct kunit *test)
    49	{
    50		if (!kasan_enabled()) {
    51			kunit_err(test, "can't run KASAN tests with KASAN disabled");
    52			return -1;
    53		}
    54	
  > 55		if (!hw_is_mode_sync()) {
    56			kunit_err(test, "can't run KASAN tests in async mode");
    57			return -1;
    58		}
    59	
    60		multishot = kasan_save_enable_multi_shot();
    61		hw_set_tagging_report_once(false);
    62		return 0;
    63	}
    64	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 25951 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20210122/5c59533d/attachment-0001.gz>