All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: jasperwang@tencent.com, kaixuxia@tencent.com,
	frankjpliu@tencent.com, kasong@tencent.com,
	sagazchen@tencent.com, kernelxing@tencent.com,
	aurelianliu@tencent.com, jason.zeng@intel.com,
	wu.zheng@intel.com, yingbao.jia@intel.com, pei.p.jia@intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: arch/arm64/mm/fault.c:743:17: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Mon, 4 Mar 2024 12:01:16 +0800	[thread overview]
Message-ID: <202403041121.daGsdMBe-lkp@intel.com> (raw)

tree:   https://gitee.com/OpenCloudOS/OpenCloudOS-Kernel.git linux-5.4/lts/5.4.119-20.0009
head:   3bf5c3f6e32e9cfe13f09bac3ae93b8e39d472c1
commit: e55f6ef6b718005b3cac70670420798aaf0174c3 ampere/arm64: Add a fixup handler for alignment faults in aarch64 code
date:   2 years, 8 months ago
config: arm64-randconfig-r131-20240303 (https://download.01.org/0day-ci/archive/20240304/202403041121.daGsdMBe-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240304/202403041121.daGsdMBe-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/202403041121.daGsdMBe-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   arch/arm64/mm/fault.c:416:24: sparse: sparse: incorrect type in return expression (different base types) @@     expected restricted vm_fault_t @@     got int @@
   arch/arm64/mm/fault.c:416:24: sparse:     expected restricted vm_fault_t
   arch/arm64/mm/fault.c:416:24: sparse:     got int
   arch/arm64/mm/fault.c:424:32: sparse: sparse: incorrect type in return expression (different base types) @@     expected restricted vm_fault_t @@     got int @@
   arch/arm64/mm/fault.c:424:32: sparse:     expected restricted vm_fault_t
   arch/arm64/mm/fault.c:424:32: sparse:     got int
   arch/arm64/mm/fault.c:426:32: sparse: sparse: incorrect type in return expression (different base types) @@     expected restricted vm_fault_t @@     got int @@
   arch/arm64/mm/fault.c:426:32: sparse:     expected restricted vm_fault_t
   arch/arm64/mm/fault.c:426:32: sparse:     got int
   arch/arm64/mm/fault.c:434:24: sparse: sparse: incorrect type in return expression (different base types) @@     expected restricted vm_fault_t @@     got int @@
   arch/arm64/mm/fault.c:434:24: sparse:     expected restricted vm_fault_t
   arch/arm64/mm/fault.c:434:24: sparse:     got int
   arch/arm64/mm/fault.c:554:13: sparse: sparse: restricted vm_fault_t degrades to integer
   arch/arm64/mm/fault.c:554:13: sparse: sparse: restricted vm_fault_t degrades to integer
   arch/arm64/mm/fault.c:616:39: sparse: sparse: restricted vm_fault_t degrades to integer
>> arch/arm64/mm/fault.c:743:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] <asn:2> * @@     got void * @@
   arch/arm64/mm/fault.c:743:17: sparse:     expected void volatile [noderef] <asn:2> *
   arch/arm64/mm/fault.c:743:17: sparse:     got void *

vim +743 arch/arm64/mm/fault.c

   730	
   731	static int align_dc_zva(unsigned long addr, struct pt_regs *regs)
   732	{
   733		int bs = read_cpuid(DCZID_EL0) & 0xf;
   734		int sz = 1 << (bs + 2);
   735	
   736		addr &= ~(sz - 1);
   737		if (is_ttbr0_addr(addr)) {
   738			for (; sz; sz--) {
   739				if (align_store(addr, 1, 0))
   740					return 1;
   741			}
   742		} else
 > 743			memset_io((void *)addr, 0, sz);
   744		return 0;
   745	}
   746	

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

             reply	other threads:[~2024-03-04  4:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04  4:01 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-05  1:14 arch/arm64/mm/fault.c:743:17: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot

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=202403041121.daGsdMBe-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aurelianliu@tencent.com \
    --cc=frankjpliu@tencent.com \
    --cc=jason.zeng@intel.com \
    --cc=jasperwang@tencent.com \
    --cc=kaixuxia@tencent.com \
    --cc=kasong@tencent.com \
    --cc=kernelxing@tencent.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pei.p.jia@intel.com \
    --cc=sagazchen@tencent.com \
    --cc=wu.zheng@intel.com \
    --cc=yingbao.jia@intel.com \
    /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.