mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Lingfeng Yang <lfy@google.com>
Cc: kbuild-all@lists.01.org,
	GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
	linux-kernel@vger.kernel.org, Alistair Delva <adelva@google.com>
Subject: [ammarfaizi2-block:google/android/kernel/common/android-4.14-stable 3332/9999] drivers/gpu/drm/virtio/virtgpu_vq.c:1130:23: sparse: sparse: incorrect type in assignment (different base types)
Date: Fri, 4 Mar 2022 14:32:46 +0800	[thread overview]
Message-ID: <202203041419.Yp7SwxGu-lkp@intel.com> (raw)

tree:   https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android-4.14-stable
head:   4ab5bac1598e3ed91a6267f6cada336467312112
commit: 4d701a3899580b291122ab7b147bc20981afd349 [3332/9999] CHROMIUM: drm/virtio: rebase zero-copy patches to virgl/drm-misc-next
config: i386-randconfig-s001-20211101 (https://download.01.org/0day-ci/archive/20220304/202203041419.Yp7SwxGu-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://github.com/ammarfaizi2/linux-block/commit/4d701a3899580b291122ab7b147bc20981afd349
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android-4.14-stable
        git checkout 4d701a3899580b291122ab7b147bc20981afd349
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/gpu/drm/virtio/

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@lists.01.org

                 reply	other threads:[~2022-03-04  6:33 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=202203041419.Yp7SwxGu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=adelva@google.com \
    --cc=gwml@vger.gnuweeb.org \
    --cc=kbuild-all@lists.01.org \
    --cc=lfy@google.com \
    --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®