From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH V3 19/19] virtio_ring: add in order support
Date: Wed, 18 Jun 2025 15:17:17 +0800 [thread overview]
Message-ID: <202506181549.sXYT8j1M-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "loongarch: unreachable instruction"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250616082518.10411-20-jasowang@redhat.com>
References: <20250616082518.10411-20-jasowang@redhat.com>
TO: Jason Wang <jasowang@redhat.com>
Hi Jason,
kernel test robot noticed the following build warnings:
[auto build test WARNING on mst-vhost/linux-next]
[also build test WARNING on linus/master v6.16-rc2 next-20250618]
[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/Jason-Wang/virtio_ring-rename-virtqueue_reinit_xxx-to-virtqueue_reset_xxx/20250616-163418
base: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
patch link: https://lore.kernel.org/r/20250616082518.10411-20-jasowang%40redhat.com
patch subject: [PATCH V3 19/19] virtio_ring: add in order support
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: loongarch-randconfig-r072-20250618 (https://download.01.org/0day-ci/archive/20250618/202506181549.sXYT8j1M-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250618/202506181549.sXYT8j1M-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202506181549.sXYT8j1M-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/virtio/virtio_ring.o: warning: objtool: detach_buf_split_in_order+0xfc: unreachable instruction
drivers/virtio/virtio_ring.o: warning: objtool: virtqueue_add_packed_in_order+0x8c: unreachable instruction
drivers/virtio/virtio_ring.o: warning: objtool: virtqueue_add_packed+0x90: unreachable instruction
drivers/virtio/virtio_ring.o: warning: objtool: virtqueue_add_split+0x88: unreachable instruction
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-06-18 7:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 7:17 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-16 8:24 [PATCH V3 00/19] virtio_ring in order support Jason Wang
2025-06-16 8:25 ` [PATCH V3 19/19] virtio_ring: add " Jason Wang
2025-07-01 6:56 ` Michael S. Tsirkin
2025-07-02 9:29 ` Jason Wang
2025-07-02 10:56 ` Michael S. Tsirkin
2025-07-03 3:13 ` Jason Wang
2025-07-03 13:49 ` Jonah Palmer
2025-07-07 3:28 ` Jason Wang
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=202506181549.sXYT8j1M-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.