From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android-4.14-stable 22/22] drivers/gpu/drm/virtio/virtgpu_vq.c:1130:23: sparse: sparse: incorrect type in assignment (different base types)
Date: Wed, 21 Apr 2021 03:10:38 +0800 [thread overview]
Message-ID: <202104210334.66ocJQts-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2793 bytes --]
tree: https://android.googlesource.com/kernel/common android-4.14-stable
head: 4d701a3899580b291122ab7b147bc20981afd349
commit: 4d701a3899580b291122ab7b147bc20981afd349 [22/22] CHROMIUM: drm/virtio: rebase zero-copy patches to virgl/drm-misc-next
config: i386-randconfig-s001-20210420 (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
git remote add android-common https://android.googlesource.com/kernel/common
git fetch --no-tags android-common android-4.14-stable
git checkout 4d701a3899580b291122ab7b147bc20981afd349
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=i386
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 >>)
drivers/gpu/drm/virtio/virtgpu_vq.c:200:33: sparse: sparse: restricted __le32 degrades to integer
drivers/gpu/drm/virtio/virtgpu_vq.c:200:43: sparse: sparse: restricted __le32 degrades to integer
>> drivers/gpu/drm/virtio/virtgpu_vq.c:1130:23: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le64 [usertype] offset @@ got unsigned long long [usertype] offset @@
drivers/gpu/drm/virtio/virtgpu_vq.c:1130:23: sparse: expected restricted __le64 [usertype] offset
drivers/gpu/drm/virtio/virtgpu_vq.c:1130:23: sparse: got unsigned long long [usertype] offset
vim +1130 drivers/gpu/drm/virtio/virtgpu_vq.c
1107
1108 void virtio_gpu_cmd_map(struct virtio_gpu_device *vgdev,
1109 struct virtio_gpu_object *bo,
1110 uint64_t offset,
1111 struct virtio_gpu_fence *fence)
1112 {
1113 struct virtio_gpu_resource_map *cmd_p;
1114 struct virtio_gpu_vbuffer *vbuf;
1115 struct virtio_gpu_resp_map_info *resp_buf;
1116
1117 resp_buf = kzalloc(sizeof(*resp_buf), GFP_KERNEL);
1118 if (!resp_buf) {
1119 DRM_ERROR("allocation failure\n");
1120 return;
1121 }
1122
1123 cmd_p = virtio_gpu_alloc_cmd_resp(vgdev,
1124 virtio_gpu_cmd_resource_map_cb, &vbuf, sizeof(*cmd_p),
1125 sizeof(struct virtio_gpu_resp_map_info), resp_buf);
1126 memset(cmd_p, 0, sizeof(*cmd_p));
1127
1128 cmd_p->hdr.type = cpu_to_le32(VIRTIO_GPU_CMD_RESOURCE_MAP);
1129 cmd_p->resource_id = cpu_to_le32(bo->hw_res_handle);
> 1130 cmd_p->offset = offset;
1131
1132 virtio_gpu_queue_fenced_ctrl_buffer(vgdev, vbuf, &cmd_p->hdr, fence);
1133 }
1134
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 30636 bytes --]
next reply other threads:[~2021-04-20 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 19:10 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-28 3:11 [android-common:android-4.14-stable 22/22] drivers/gpu/drm/virtio/virtgpu_vq.c:1130:23: sparse: sparse: incorrect type in assignment (different base types) kernel test robot
2021-07-29 11:05 kernel test robot
2020-07-07 4:11 kernel test robot
2020-05-27 7:19 kbuild test robot
2020-05-19 0:00 kbuild 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=202104210334.66ocJQts-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.