linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Ben Hutchings <bwh@kernel.org>
Subject: drivers/ide/ide-ioctls.c:15:24: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Fri, 22 May 2020 20:23:52 +0800	[thread overview]
Message-ID: <202005222050.mkKQBFyc%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4364 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   051143e1602d90ea71887d92363edd539d411de5
commit: 1df23c6fe5b0654ece219985a0c32e40b100bd9a compat_ioctl: move HDIO ioctl handling into drivers/ide
date:   5 months ago
config: xtensa-randconfig-s002-20200522 (attached as .config)
compiler: xtensa-linux-gcc (GCC) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-193-gb8fad4bc-dirty
        git checkout 1df23c6fe5b0654ece219985a0c32e40b100bd9a
        # save the attached .config to linux build tree
        make W=1 C=1 ARCH=xtensa CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

   ./arch/xtensa/include/generated/uapi/asm/unistd_32.h:391:41: sparse: sparse: no newline at end of file
>> drivers/ide/ide-ioctls.c:15:24: sparse: sparse: incorrect type in initializer (different address spaces) @@    expected signed int *__pu_addr @@    got signed int [noderef] [usertypsigned int *__pu_addr @@
>> drivers/ide/ide-ioctls.c:15:24: sparse:    expected signed int *__pu_addr
>> drivers/ide/ide-ioctls.c:15:24: sparse:    got signed int [noderef] [usertype] <asn:1> *
>> drivers/ide/ide-ioctls.c:15:24: sparse: sparse: incorrect type in argument 1 (different address spaces) @@    expected void [noderef] <asn:1> *to @@    got f] <asn:1> *to @@
   drivers/ide/ide-ioctls.c:15:24: sparse:    expected void [noderef] <asn:1> *to
>> drivers/ide/ide-ioctls.c:15:24: sparse:    got signed int *__pu_addr
   drivers/ide/ide-ioctls.c:17:16: sparse: sparse: incorrect type in initializer (different address spaces) @@    expected long *__pu_addr @@    got long [noderef] <aslong *__pu_addr @@
   drivers/ide/ide-ioctls.c:17:16: sparse:    expected long *__pu_addr
   drivers/ide/ide-ioctls.c:17:16: sparse:    got long [noderef] <asn:1> *
   drivers/ide/ide-ioctls.c:17:16: sparse: sparse: incorrect type in argument 1 (different address spaces) @@    expected void [noderef] <asn:1> *to @@    got n:1> *to @@
   drivers/ide/ide-ioctls.c:17:16: sparse:    expected void [noderef] <asn:1> *to
   drivers/ide/ide-ioctls.c:17:16: sparse:    got long *__pu_addr
   include/linux/ata.h:1101:34: sparse: sparse: incorrect type in assignment (different base types) @@    expected unsigned short [usertype] @@    got resunsigned short [usertype] @@
   include/linux/ata.h:1101:34: sparse:    expected unsigned short [usertype]
   include/linux/ata.h:1101:34: sparse:    got restricted __le16 [usertype]
   include/linux/ata.h:1102:34: sparse: sparse: incorrect type in assignment (different base types) @@    expected unsigned short [usertype] @@    got resunsigned short [usertype] @@
   include/linux/ata.h:1102:34: sparse:    expected unsigned short [usertype]
   include/linux/ata.h:1102:34: sparse:    got restricted __le16 [usertype]
   include/linux/ata.h:1103:34: sparse: sparse: incorrect type in assignment (different base types) @@    expected unsigned short [usertype] @@    got resunsigned short [usertype] @@
   include/linux/ata.h:1103:34: sparse:    expected unsigned short [usertype]
   include/linux/ata.h:1103:34: sparse:    got restricted __le16 [usertype]
   include/linux/ata.h:1104:34: sparse: sparse: incorrect type in assignment (different base types) @@    expected unsigned short [usertype] @@    got resunsigned short [usertype] @@
   include/linux/ata.h:1104:34: sparse:    expected unsigned short [usertype]
   include/linux/ata.h:1104:34: sparse:    got restricted __le16 [usertype]
   include/linux/ata.h:1105:34: sparse: sparse: incorrect type in assignment (different base types) @@    expected unsigned short [usertype] @@    got resunsigned short [usertype] @@
   include/linux/ata.h:1105:34: sparse:    expected unsigned short [usertype]
   include/linux/ata.h:1105:34: sparse:    got restricted __le16 [usertype]

vim +15 drivers/ide/ide-ioctls.c

    11	
    12	static int put_user_long(long val, unsigned long arg)
    13	{
    14		if (in_compat_syscall())
  > 15			return put_user(val, (compat_long_t __user *)compat_ptr(arg));
    16	
    17		return put_user(val, (long __user *)arg);
    18	}
    19	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34001 bytes --]

             reply	other threads:[~2020-05-22 12:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 12:23 kbuild test robot [this message]
2020-05-22 13:40 ` drivers/ide/ide-ioctls.c:15:24: sparse: sparse: incorrect type in initializer (different address spaces) Arnd Bergmann
2020-05-22 15:39   ` Al Viro

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=202005222050.mkKQBFyc%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=arnd@arndb.de \
    --cc=bwh@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).