linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	David Sterba <dsterba@suse.com>
Subject: [linux-next:master 3345/4062] arch/um/kernel/skas/uaccess.c:358:9: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Fri, 17 Jun 2022 03:24:12 +0800	[thread overview]
Message-ID: <202206170317.wxLpoEbx-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   c6d7e3b385f19869ab96e9404c92ff1abc34f2c8
commit: 20adc3e8f39ad4ce68795b6d3f9847f45ccd931a [3345/4062] highmem: Make kunmap_{local,atomic}() take pointers to const void
config: um-i386_defconfig (https://download.01.org/0day-ci/archive/20220617/202206170317.wxLpoEbx-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-30-g92122700-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=20adc3e8f39ad4ce68795b6d3f9847f45ccd931a
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 20adc3e8f39ad4ce68795b6d3f9847f45ccd931a
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=um SUBARCH=i386 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
   arch/um/kernel/skas/uaccess.c:273:15: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected unsigned int [noderef] [usertype] __user *uaddr @@     got unsigned int [usertype] * @@
   arch/um/kernel/skas/uaccess.c:273:15: sparse:     expected unsigned int [noderef] [usertype] __user *uaddr
   arch/um/kernel/skas/uaccess.c:273:15: sparse:     got unsigned int [usertype] *
   arch/um/kernel/skas/uaccess.c:348:15: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected unsigned int [noderef] [usertype] __user *uaddr @@     got void * @@
   arch/um/kernel/skas/uaccess.c:348:15: sparse:     expected unsigned int [noderef] [usertype] __user *uaddr
   arch/um/kernel/skas/uaccess.c:348:15: sparse:     got void *
   arch/um/kernel/skas/uaccess.c:353:15: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void const volatile *v @@     got unsigned int [noderef] [usertype] __user *__ai_ptr @@
   arch/um/kernel/skas/uaccess.c:353:15: sparse:     expected void const volatile *v
   arch/um/kernel/skas/uaccess.c:353:15: sparse:     got unsigned int [noderef] [usertype] __user *__ai_ptr
   arch/um/kernel/skas/uaccess.c:353:15: sparse: sparse: cast removes address space '__user' of expression
   arch/um/kernel/skas/uaccess.c:353:15: sparse: sparse: cast removes address space '__user' of expression
   arch/um/kernel/skas/uaccess.c:353:15: sparse: sparse: cast removes address space '__user' of expression
   arch/um/kernel/skas/uaccess.c:353:15: sparse: sparse: cast removes address space '__user' of expression
>> arch/um/kernel/skas/uaccess.c:358:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void const *addr @@     got unsigned int [noderef] [usertype] __user *uaddr @@
   arch/um/kernel/skas/uaccess.c:358:9: sparse:     expected void const *addr
   arch/um/kernel/skas/uaccess.c:358:9: sparse:     got unsigned int [noderef] [usertype] __user *uaddr
   arch/um/kernel/skas/uaccess.c:274:19: sparse: sparse: dereference of noderef expression
   arch/um/kernel/skas/uaccess.c:280:18: sparse: sparse: dereference of noderef expression
   arch/um/kernel/skas/uaccess.c:283:18: sparse: sparse: dereference of noderef expression
   arch/um/kernel/skas/uaccess.c:286:18: sparse: sparse: dereference of noderef expression
   arch/um/kernel/skas/uaccess.c:289:18: sparse: sparse: dereference of noderef expression
   arch/um/kernel/skas/uaccess.c:292:18: sparse: sparse: dereference of noderef expression
   arch/um/kernel/skas/uaccess.c:351:18: sparse: sparse: dereference of noderef expression

vim +358 arch/um/kernel/skas/uaccess.c

dd3035a21ba7cc Anton Ivanov 2021-03-12  350  
dd3035a21ba7cc Anton Ivanov 2021-03-12  351  	*uval = *uaddr;
dd3035a21ba7cc Anton Ivanov 2021-03-12  352  
dd3035a21ba7cc Anton Ivanov 2021-03-12  353  	ret = cmpxchg(uaddr, oldval, newval);
dd3035a21ba7cc Anton Ivanov 2021-03-12  354  
dd3035a21ba7cc Anton Ivanov 2021-03-12  355  #ifdef CONFIG_64BIT
dd3035a21ba7cc Anton Ivanov 2021-03-12  356  	pagefault_enable();
dd3035a21ba7cc Anton Ivanov 2021-03-12  357  #else
dd3035a21ba7cc Anton Ivanov 2021-03-12 @358  	kunmap_atomic(uaddr);

:::::: The code at line 358 was first introduced by commit
:::::: dd3035a21ba7ccaa883d7107d357ad06320d78fc um: add a UML specific futex implementation

:::::: TO: Anton Ivanov <anton.ivanov@cambridgegreys.com>
:::::: CC: Richard Weinberger <richard@nod.at>

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp


                 reply	other threads:[~2022-06-16 19:25 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=202206170317.wxLpoEbx-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dsterba@suse.com \
    --cc=fmdefrancesco@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    /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