From: kernel test robot <lkp@intel.com>
To: Dave Wysochanski <dwysocha@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
David Howells <dhowells@redhat.com>
Subject: [dhowells-fs:fscache-rewrite-indexing-3 60/63] fs/nfs/fscache.c:58:51: sparse: sparse: incorrect type in argument 3 (different base types)
Date: Sat, 27 Nov 2021 14:07:22 +0800 [thread overview]
Message-ID: <202111271427.AQQrX7DH-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git fscache-rewrite-indexing-3
head: 7cb6fc11f97e7d40213fb323f0474fdf5ce4ff24
commit: d3292e579b1e9fd57f6f7716e9d01a13144db386 [60/63] nfs: Convert to new fscache volume/cookie API
config: s390-randconfig-s032-20211126 (https://download.01.org/0day-ci/archive/20211127/202111271427.AQQrX7DH-lkp@intel.com/config)
compiler: s390-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/dhowells/linux-fs.git/commit/?id=d3292e579b1e9fd57f6f7716e9d01a13144db386
git remote add dhowells-fs https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
git fetch --no-tags dhowells-fs fscache-rewrite-indexing-3
git checkout d3292e579b1e9fd57f6f7716e9d01a13144db386
# save the config file 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=s390 SHELL=/bin/bash fs/nfs/
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 >>)
>> fs/nfs/fscache.c:58:51: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected unsigned long long x @@ got restricted __be16 const [usertype] sin_port @@
fs/nfs/fscache.c:58:51: sparse: expected unsigned long long x
fs/nfs/fscache.c:58:51: sparse: got restricted __be16 const [usertype] sin_port
>> fs/nfs/fscache.c:59:61: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected unsigned long long x @@ got restricted __be32 const [usertype] s_addr @@
fs/nfs/fscache.c:59:61: sparse: expected unsigned long long x
fs/nfs/fscache.c:59:61: sparse: got restricted __be32 const [usertype] s_addr
>> fs/nfs/fscache.c:64:52: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected unsigned long long x @@ got restricted __be16 const [usertype] sin6_port @@
fs/nfs/fscache.c:64:52: sparse: expected unsigned long long x
fs/nfs/fscache.c:64:52: sparse: got restricted __be16 const [usertype] sin6_port
>> fs/nfs/fscache.c:65:73: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected unsigned long long x @@ got restricted __be32 const @@
fs/nfs/fscache.c:65:73: sparse: expected unsigned long long x
fs/nfs/fscache.c:65:73: sparse: got restricted __be32 const
fs/nfs/fscache.c:66:73: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected unsigned long long x @@ got restricted __be32 const @@
fs/nfs/fscache.c:66:73: sparse: expected unsigned long long x
fs/nfs/fscache.c:66:73: sparse: got restricted __be32 const
fs/nfs/fscache.c:67:73: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected unsigned long long x @@ got restricted __be32 const @@
fs/nfs/fscache.c:67:73: sparse: expected unsigned long long x
fs/nfs/fscache.c:67:73: sparse: got restricted __be32 const
fs/nfs/fscache.c:68:73: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected unsigned long long x @@ got restricted __be32 const @@
fs/nfs/fscache.c:68:73: sparse: expected unsigned long long x
fs/nfs/fscache.c:68:73: sparse: got restricted __be32 const
vim +58 fs/nfs/fscache.c
37
38 /*
39 * Get the per-client index cookie for an NFS client if the appropriate mount
40 * flag was set
41 * - We always try and get an index cookie for the client, but get filehandle
42 * cookies on a per-superblock basis, depending on the mount flags
43 */
44 static bool nfs_fscache_get_client_key(struct nfs_client *clp,
45 char *key, int *_len)
46 {
47 const struct sockaddr_in6 *sin6 = (struct sockaddr_in6 *) &clp->cl_addr;
48 const struct sockaddr_in *sin = (struct sockaddr_in *) &clp->cl_addr;
49
50 *_len += snprintf(key + *_len, NFS_MAX_KEY_LEN - *_len,
51 ",%u.%u,%x",
52 clp->rpc_ops->version,
53 clp->cl_minorversion,
54 clp->cl_addr.ss_family);
55
56 switch (clp->cl_addr.ss_family) {
57 case AF_INET:
> 58 if (!nfs_append_int(key, _len, sin->sin_port) ||
> 59 !nfs_append_int(key, _len, sin->sin_addr.s_addr))
60 return false;
61 return true;
62
63 case AF_INET6:
> 64 if (!nfs_append_int(key, _len, sin6->sin6_port) ||
> 65 !nfs_append_int(key, _len, sin6->sin6_addr.s6_addr32[0]) ||
66 !nfs_append_int(key, _len, sin6->sin6_addr.s6_addr32[1]) ||
67 !nfs_append_int(key, _len, sin6->sin6_addr.s6_addr32[2]) ||
68 !nfs_append_int(key, _len, sin6->sin6_addr.s6_addr32[3]))
69 return false;
70 return true;
71
72 default:
73 printk(KERN_WARNING "NFS: Unknown network family '%d'\n",
74 clp->cl_addr.ss_family);
75 return false;
76 }
77 }
78
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-11-27 6: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=202111271427.AQQrX7DH-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=dwysocha@redhat.com \
--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
all inboxes | Powered by JetHome®