automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: Cheng1.jiang@intel.com, robot@bytheb.org
Subject: |FAILURE| pw126336 [PATCH 2/2] vhost: add egress API for port mirroring datapath
Date: Thu, 20 Apr 2023 22:39:33 -0400	[thread overview]
Message-ID: <20230421023933.649493-1-robot@bytheb.org> (raw)
In-Reply-To: <20230421010932.46847-3-cheng1.jiang@intel.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/126336/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4760644662
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-clang-asan+doc+tests" failed at step Build and test
"fedora:35-clang" failed at step Build
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-clang-asan+doc+tests" at step Build and test
####################################################################################
                                        ^
../lib/vhost/virtio_net.c:4670:40: error: reading variable 'async' requires holding any mutex [-Werror,-Wthread-safety-analysis]
        struct vhost_async *mr_async = mr_vq->async;
                                              ^
../lib/vhost/virtio_net.c:4692:16: error: calling function 'reserve_avail_buf_split' requires holding mutex 'vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
                if (unlikely(reserve_avail_buf_split(dev, vq, pkt_len, buf_vec,
                             ^
../lib/vhost/virtio_net.c:4700:16: error: calling function 'reserve_avail_buf_split' requires holding mutex 'mr_vq->iotlb_lock' [-Werror,-Wthread-safety-analysis]
                if (unlikely(reserve_avail_buf_split(mr_dev, mr_vq, pkt_len, mr_buf_vec,
                             ^
../lib/vhost/virtio_net.c:4735:11: error: calling function 'vhost_async_dma_transfer' requires holding mutex 'vq->access_lock' exclusively [-Werror,-Wthread-safety-analysis]
        n_xfer = vhost_async_dma_transfer(dev, vq, dma_id, vchan_id, async->pkts_idx,
                 ^
../lib/vhost/virtio_net.c:4821:6: error: mutex 'vq->iotlb_lock' is not held on every path through here [-Werror,-Wthread-safety-analysis]
        if (mr_dev->features & (1ULL << VIRTIO_F_IOMMU_PLATFORM))
            ^
../lib/vhost/virtio_net.c:4820:3: note: mutex acquired here
                vhost_user_iotlb_rd_lock(vq);
                ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
[417/4342] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost.c.o'.
[418/4342] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_crypto.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-clang-asan+doc+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "fedora:35-clang" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:35-clang" at step Build
####################################################################################
--------------------------------END LOGS-----------------------------

      parent reply	other threads:[~2023-04-21  2:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230421010932.46847-3-cheng1.jiang@intel.com>
2023-04-21  1:34 ` |SUCCESS| pw126335-126336 " qemudev
2023-04-21  1:38 ` qemudev
2023-04-21  1:44 ` |WARNING| pw126336 " checkpatch
2023-04-21  2:39 ` 0-day Robot [this message]

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=20230421023933.649493-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=Cheng1.jiang@intel.com \
    --cc=test-report@dpdk.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;
as well as URLs for NNTP newsgroup(s).