From: Arnd Bergmann <arnd@arndb.de>
To: kernel test robot <lkp@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [linux-next:master 6322/7526] arch/riscv/kernel/perf_callchain.c:19:26: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Wed, 23 Feb 2022 20:22:11 +0100 [thread overview]
Message-ID: <CAK8P3a0LiL8fOD_CqOz-9fdetK_VF666gHWfpGUQLJwX6rDZ8Q@mail.gmail.com> (raw)
In-Reply-To: <202202240123.jVKXO4uv-lkp@intel.com>
On Wed, Feb 23, 2022 at 6:02 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 196d330d7fb1e7cc0d85641c89ce4602cb36f12e
> commit: 27e8140d7819b7dce32967e4b5bba102b59196ee [6322/7526] uaccess: fix type mismatch warnings from access_ok()
> config: riscv-randconfig-s032-20220223 (https://download.01.org/0day-ci/archive/20220224/202202240123.jVKXO4uv-lkp@intel.com/config)
> compiler: riscv64-linux-gcc (GCC) 11.2.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # apt-get install sparse
> # sparse version: v0.6.4-dirty
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=27e8140d7819b7dce32967e4b5bba102b59196ee
> 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 27e8140d7819b7dce32967e4b5bba102b59196ee
> # save the config file to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=riscv SHELL=/bin/bash arch/riscv/kernel/
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
>
> sparse warnings: (new ones prefixed by >>)
> >> arch/riscv/kernel/perf_callchain.c:19:26: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected unsigned long [noderef] __user *user_frame_tail @@ got unsigned long * @@
> arch/riscv/kernel/perf_callchain.c:19:26: sparse: expected unsigned long [noderef] __user *user_frame_tail
> arch/riscv/kernel/perf_callchain.c:19:26: sparse: got unsigned long *
Fixed now, thanks for the report!
Arnd
prev parent reply other threads:[~2022-02-23 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 17:02 kernel test robot
2022-02-23 19:22 ` Arnd Bergmann [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=CAK8P3a0LiL8fOD_CqOz-9fdetK_VF666gHWfpGUQLJwX6rDZ8Q@mail.gmail.com \
--to=arnd@arndb.de \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox