From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: kernel test robot <lkp@intel.com>
Cc: <kbuild-all@lists.01.org>, <linux-kernel@vger.kernel.org>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
Subject: Re: arch/arm/mm/fault.c:210:24: sparse: sparse: incorrect type in return expression (different base types)
Date: Wed, 17 Nov 2021 10:15:30 +0800 [thread overview]
Message-ID: <7ae0d25e-4baa-76e2-4937-9b413af25591@huawei.com> (raw)
In-Reply-To: <202111170449.8KzXziyR-lkp@intel.com>
https://lore.kernel.org/linux-arm-kernel/20211115075834.156838-1-wangkefeng.wang@huawei.com/
On 2021/11/17 4:14, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 8ab774587903771821b59471cc723bba6d893942
> commit: caed89dab0ca0e73d7e016c04e1f5957650f4ec3 ARM: 9128/1: mm: Refactor the __do_page_fault()
> date: 4 weeks ago
> config: arm-randconfig-s031-20211116 (attached as .config)
> compiler: arm-linux-gnueabi-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/torvalds/linux.git/commit/?id=caed89dab0ca0e73d7e016c04e1f5957650f4ec3
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout caed89dab0ca0e73d7e016c04e1f5957650f4ec3
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arm SHELL=/bin/bash arch/arm/mm/
>
> 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/arm/mm/fault.c:210:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted vm_fault_t @@ got int @@
> arch/arm/mm/fault.c:210:24: sparse: expected restricted vm_fault_t
> arch/arm/mm/fault.c:210:24: sparse: got int
> arch/arm/mm/fault.c:214:32: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted vm_fault_t @@ got int @@
> arch/arm/mm/fault.c:214:32: sparse: expected restricted vm_fault_t
> arch/arm/mm/fault.c:214:32: sparse: got int
> arch/arm/mm/fault.c:216:32: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted vm_fault_t @@ got int @@
> arch/arm/mm/fault.c:216:32: sparse: expected restricted vm_fault_t
> arch/arm/mm/fault.c:216:32: sparse: got int
> arch/arm/mm/fault.c:218:32: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted vm_fault_t @@ got int @@
> arch/arm/mm/fault.c:218:32: sparse: expected restricted vm_fault_t
> arch/arm/mm/fault.c:218:32: sparse: got int
> arch/arm/mm/fault.c:226:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted vm_fault_t @@ got int @@
> arch/arm/mm/fault.c:226:24: sparse: expected restricted vm_fault_t
> arch/arm/mm/fault.c:226:24: sparse: got int
> arch/arm/mm/fault.c:312:13: sparse: sparse: restricted vm_fault_t degrades to integer
> arch/arm/mm/fault.c:312:13: sparse: sparse: restricted vm_fault_t degrades to integer
> arch/arm/mm/fault.c:345:24: sparse: sparse: restricted vm_fault_t degrades to integer
>
next prev parent reply other threads:[~2021-11-17 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 20:14 kernel test robot
2021-11-17 2:15 ` Kefeng Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-15 4:55 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=7ae0d25e-4baa-76e2-4937-9b413af25591@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rmk+kernel@armlinux.org.uk \
/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
all inboxes | Powered by JetHome®