DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 676] Cryptodev test build warning on Fedora 34
Date: Wed, 14 Apr 2021 13:00:03 +0000	[thread overview]
Message-ID: <bug-676-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=676

            Bug ID: 676
           Summary: Cryptodev test build warning on Fedora 34
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: cryptodev
          Assignee: dev@dpdk.org
          Reporter: kevuzaj@gmail.com
  Target Milestone: ---

Cryptodev tests have build warnings on Fedora-34_Beta-1.3 with the latest
packages.

[kevin@fedora ~]$ cat /etc/redhat-release 
Fedora release 34 (Thirty Four)
[kevin@fedora ~]$ uname -a
Linux fedora 5.11.13-300.fc34.x86_64 #1 SMP Sun Apr 11 15:07:42 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux
[kevin@fedora ~]$ gcc --version
gcc (GCC) 11.0.1 20210324 (Red Hat 11.0.1-0)



591/2712] Compiling C object app/test/dpdk-test.p/test_cryptodev.c.o
../app/test/test_cryptodev.c: In function ‘test_multi_session’:
../app/test/test_cryptodev.c:10448:9: warning: array subscript ‘struct
rte_cryptodev_sym_session *[4]’ is partly outside array bounds of ‘unsigned
char[33]’ [-Warray-bounds]
10448 |         rte_cryptodev_sym_session_init(ts_params->valid_devs[0],
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10449 |                         sessions[i], &ut_params->auth_xform,
      |                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10450 |                         ts_params->session_priv_mpool);
      |                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../app/test/test_cryptodev.c:10400:20: note: referencing an object of size 33
allocated by ‘rte_malloc’
10400 |         sessions = rte_malloc(NULL,
      |                    ^~~~~~~~~~~~~~~~
10401 |                         (sizeof(struct rte_cryptodev_sym_session *) *
      |                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10402 |                         MAX_NB_SESSIONS) + 1, 0);
      |                         ~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ../app/test/test.h:25,
                 from ../app/test/test_cryptodev.c:29:
../app/test/test_cryptodev.c:10451:34: warning: array subscript ‘struct
rte_cryptodev_sym_session *[4]’ is partly outside array bounds of ‘unsigned
char[33]’ [-Warray-bounds]
10451 |         TEST_ASSERT_NULL(sessions[i],
      |                          ~~~~~~~~^~~
../lib/librte_eal/include/rte_test.h:20:15: note: in definition of macro
‘RTE_TEST_ASSERT’
   20 |         if (!(cond)) {                                                 
      \
      |               ^~~~
../app/test/test.h:103:26: note: in expansion of macro ‘RTE_TEST_ASSERT_NULL’
  103 | #define TEST_ASSERT_NULL RTE_TEST_ASSERT_NULL
      |                          ^~~~~~~~~~~~~~~~~~~~
../app/test/test_cryptodev.c:10451:9: note: in expansion of macro
‘TEST_ASSERT_NULL’
10451 |         TEST_ASSERT_NULL(sessions[i],
      |         ^~~~~~~~~~~~~~~~
../app/test/test_cryptodev.c:10400:20: note: referencing an object of size 33
allocated by ‘rte_malloc’
10400 |         sessions = rte_malloc(NULL,
      |                    ^~~~~~~~~~~~~~~~
10401 |                         (sizeof(struct rte_cryptodev_sym_session *) *
      |                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10402 |                         MAX_NB_SESSIONS) + 1, 0);
      |                         ~~~~~~~~~~~~~~~~~~~~~~~~

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-04-14 13:00 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=bug-676-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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).