From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 3985/7050] drivers/net/bareudp.c:227:14: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Mon, 9 Mar 2020 04:39:02 +0800 [thread overview]
Message-ID: <202003090459.30E1KR4T%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b86a6a241b7c60ca7a6ca4fb3c0d2aedbbf2c1b6
commit: 571912c69f0ed731bd1e071ade9dc7ca4aa52065 [3985/7050] net: UDP tunnel encapsulation module for tunnelling different protocols like MPLS, IP, NSH etc.
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-174-g094d5a94-dirty
git checkout 571912c69f0ed731bd1e071ade9dc7ca4aa52065
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/net/bareudp.c:227:14: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct socket *sock @@ got struct socket [nodstruct socket *sock @@
drivers/net/bareudp.c:227:14: sparse: expected struct socket *sock
drivers/net/bareudp.c:227:14: sparse: got struct socket [noderef] <asn:4> *sock
>> drivers/net/bareudp.c:512:28: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be16 [usertype] port @@ got 16 [usertype] port @@
drivers/net/bareudp.c:512:28: sparse: expected restricted __be16 [usertype] port
drivers/net/bareudp.c:512:28: sparse: got unsigned short
>> drivers/net/bareudp.c:515:33: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be16 [usertype] ethertype @@ got 16 [usertype] ethertype @@
drivers/net/bareudp.c:515:33: sparse: expected restricted __be16 [usertype] ethertype
drivers/net/bareudp.c:515:33: sparse: got unsigned short
vim +227 drivers/net/bareudp.c
222
223 static void bareudp_sock_release(struct bareudp_dev *bareudp)
224 {
225 struct socket *sock;
226
> 227 sock = bareudp->sock;
228 rcu_assign_pointer(bareudp->sock, NULL);
229 synchronize_net();
230 udp_tunnel_sock_release(sock);
231 }
232
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-03-08 20:39 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=202003090459.30E1KR4T%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--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