All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android11-5.4 1/1] arch/arm/mm/fault.c:28:6: sparse: sparse: symbol 'copy_from_kernel_nofault_allowed' was not declared. Should it be static?
Date: Tue, 29 Apr 2025 23:08:40 +0800	[thread overview]
Message-ID: <202504292248.4b9Un345-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android11-5.4
head:   1aec9e76fe4a65b0a26fa1b30bdb3400d9728b2d
commit: 11bb05969b19050a0f9baa6bcd1cb23439b267e3 [1/1] ARM: 9350/1: fault: Implement copy_from_kernel_nofault_allowed()
config: arm-randconfig-r111-20250429 (https://download.01.org/0day-ci/archive/20250429/202504292248.4b9Un345-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
reproduce: (https://download.01.org/0day-ci/archive/20250429/202504292248.4b9Un345-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/202504292248.4b9Un345-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> arch/arm/mm/fault.c:28:6: sparse: sparse: symbol 'copy_from_kernel_nofault_allowed' was not declared. Should it be static?
   arch/arm/mm/fault.c:217:15: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted vm_fault_t [usertype] fault @@     got int @@
   arch/arm/mm/fault.c:217:15: sparse:     expected restricted vm_fault_t [usertype] fault
   arch/arm/mm/fault.c:217:15: sparse:     got int
   arch/arm/mm/fault.c:229:23: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted vm_fault_t [usertype] fault @@     got int @@
   arch/arm/mm/fault.c:229:23: sparse:     expected restricted vm_fault_t [usertype] fault
   arch/arm/mm/fault.c:229:23: sparse:     got int
   arch/arm/mm/fault.c:342:13: sparse: sparse: restricted vm_fault_t degrades to integer
   arch/arm/mm/fault.c:342:13: sparse: sparse: restricted vm_fault_t degrades to integer
   arch/arm/mm/fault.c:375:24: sparse: sparse: restricted vm_fault_t degrades to integer

vim +/copy_from_kernel_nofault_allowed +28 arch/arm/mm/fault.c

    27	
  > 28	bool copy_from_kernel_nofault_allowed(const void *unsafe_src, size_t size)
    29	{
    30		unsigned long addr = (unsigned long)unsafe_src;
    31	
    32		return addr >= TASK_SIZE && ULONG_MAX - addr >= size;
    33	}
    34	

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

                 reply	other threads:[~2025-04-29 15:09 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=202504292248.4b9Un345-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --cc=oe-kbuild-all@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 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.