From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |FAILURE| pw133513 [PATCH] Add bus master enable/disable APIs for CD
Date: Fri, 27 Oct 2023 15:57:45 -0700 (PDT) [thread overview]
Message-ID: <653c4069.050a0220.66520.7aadSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/133513
_Testing issues_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Friday, October 27 2023 16:22:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:656dfad43136ef43f4315ab6ed45b78b68c287a7
133513 --> testing fail
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
==== 20 line log output for CentOS Stream 9 (ARM) (dpdk_meson_compile): ====
../drivers/bus/cdx/cdx_vfio.c:677:24: error: array subscript 0 is outside array bounds of 'struct vfio_device_feature[0]' [-Werror=array-bounds]
677 | feature->flags |= VFIO_DEVICE_FEATURE_SET;
| ^
../drivers/bus/cdx/cdx_vfio.c:668:49: note: referencing an object of size 0 allocated by 'malloc'
668 | feature = (struct vfio_device_feature *)malloc(argsz);
| ^~~~~~~~~~~~~
../drivers/bus/cdx/cdx_vfio.c:686:16: error: array subscript 0 is outside array bounds of 'struct vfio_device_feature[0]' [-Werror=array-bounds]
686 | feature->flags = RTE_VFIO_DEVICE_FEATURE_BUS_MASTER | VFIO_DEVICE_FEATURE_SET;
| ^~
../drivers/bus/cdx/cdx_vfio.c:668:49: note: referencing an object of size 0 allocated by 'malloc'
668 | feature = (struct vfio_device_feature *)malloc(argsz);
| ^~~~~~~~~~~~~
../drivers/bus/cdx/cdx_vfio.c:687:24: error: array subscript 2 is outside array bounds of 'struct vfio_device_feature[0]' [-Werror=array-bounds]
687 | vfio_bm_feature->op = VFIO_DEVICE_FEATURE_CLEAR_MASTER;
| ^~
../drivers/bus/cdx/cdx_vfio.c:668:49: note: referencing an object of size 0 allocated by 'malloc'
668 | feature = (struct vfio_device_feature *)malloc(argsz);
| ^~~~~~~~~~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28117/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-27 22:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 22:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-28 0:08 dpdklab
2023-10-27 23:31 dpdklab
2023-10-27 23:31 dpdklab
2023-10-27 23:30 dpdklab
2023-10-27 23:05 dpdklab
2023-10-27 23:05 dpdklab
2023-10-27 23:04 dpdklab
2023-10-27 23:04 dpdklab
2023-10-27 23:03 dpdklab
2023-10-27 23:03 dpdklab
2023-10-27 23:03 dpdklab
2023-10-27 23:03 dpdklab
2023-10-27 23:02 dpdklab
2023-10-27 23:00 dpdklab
2023-10-27 22:59 dpdklab
2023-10-27 22:59 dpdklab
2023-10-27 22:58 dpdklab
2023-10-27 22:58 dpdklab
2023-10-27 22:58 dpdklab
2023-10-27 22:58 dpdklab
2023-10-27 22:58 dpdklab
2023-10-27 22:57 dpdklab
2023-10-27 22:57 dpdklab
2023-10-27 22:57 dpdklab
2023-10-27 22:56 dpdklab
2023-10-27 22:56 dpdklab
2023-10-27 22:56 dpdklab
2023-10-27 22:55 dpdklab
2023-10-27 22:50 dpdklab
2023-10-27 22:50 dpdklab
2023-10-27 22:49 dpdklab
2023-10-27 22:49 dpdklab
2023-10-27 22:48 dpdklab
2023-10-27 22:48 dpdklab
2023-10-27 22:47 dpdklab
2023-10-27 22:47 dpdklab
2023-10-27 22:46 dpdklab
2023-10-27 22:46 dpdklab
2023-10-27 22:46 dpdklab
2023-10-27 22:43 dpdklab
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=653c4069.050a0220.66520.7aadSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.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).