linux-kernel - Re: [PATCH v2 1/2] virtio: abstract virtqueue related methods

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <202305180109.U6SyyRS2-lkp@intel.com>
Date:   Thu, 18 May 2023 01:59:48 +0800
From:   kernel test robot <lkp@...el.com>
To:     zhenwei pi <pizhenwei@...edance.com>, stefanha@...hat.com,
        mst@...hat.com, jasowang@...hat.com
Cc:     oe-kbuild-all@...ts.linux.dev, xuanzhuo@...ux.alibaba.com,
        virtualization@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org, zhenwei pi <pizhenwei@...edance.com>
Subject: Re: [PATCH v2 1/2] virtio: abstract virtqueue related methods

Hi zhenwei,

kernel test robot noticed the following build errors:

[auto build test ERROR on mst-vhost/linux-next]
[also build test ERROR on linus/master v6.4-rc2 next-20230517]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/zhenwei-pi/virtio-abstract-virtqueue-related-methods/20230517-110311
base:   https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
patch link:    https://lore.kernel.org/r/20230517025424.601141-2-pizhenwei%40bytedance.com
patch subject: [PATCH v2 1/2] virtio: abstract virtqueue related methods
config: loongarch-randconfig-r004-20230517
compiler: loongarch64-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/intel-lab-lkp/linux/commit/146086b281eebe5c5368c387f96a0395c6252d41
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review zhenwei-pi/virtio-abstract-virtqueue-related-methods/20230517-110311
        git checkout 146086b281eebe5c5368c387f96a0395c6252d41
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=loongarch olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=loongarch SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202305180109.U6SyyRS2-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from drivers/gpu/drm/virtio/virtgpu_drv.h:30,
                    from drivers/gpu/drm/virtio/virtgpu_drv.c:41:
   include/linux/virtio.h: In function 'virtio_break_device':
>> include/linux/virtio.h:492:19: error: 'struct virtqueue' has no member named '__builtin_loongarch_break'
     492 |                 vq->__break(vq);
         |                   ^~


vim +492 include/linux/virtio.h

   481	
   482	/*
   483	 * This should prevent the device from being used, allowing drivers to
   484	 * recover.  You may need to grab appropriate locks to flush.
   485	 */
   486	static inline void virtio_break_device(struct virtio_device *dev)
   487	{
   488		struct virtqueue *vq;
   489	
   490		spin_lock(&dev->vqs_list_lock);
   491		list_for_each_entry(vq, &dev->vqs, list) {
 > 492			vq->__break(vq);
   493		}
   494		spin_unlock(&dev->vqs_list_lock);
   495	}
   496	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

View attachment "config" of type "text/plain" (159563 bytes)