DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1724] test_pktmbuf_read_from_offset tests for incorrect overflow behaviour of rte_pktmbuf_read
Date: Mon, 16 Jun 2025 14:41:21 +0000	[thread overview]
Message-ID: <bug-1724-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]

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

            Bug ID: 1724
           Summary: test_pktmbuf_read_from_offset tests for incorrect
                    overflow behaviour of rte_pktmbuf_read
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: marat.khalili@huawei.com
  Target Milestone: ---

Test function test_pktmbuf_read_from_offset as one of its checks
surprisingly verifies that the following call succeeds even though
rte_pktmbuf_read never guarantees this behaviour in its documentation:

    rte_pktmbuf_read(m, hdr_len, UINT_MAX, NULL);

The reason this call succeeds is due to 32-bit unsigned integer
overflow, but it is unlikely that this behaviour is intentional and
needs testing. It is very likely instead that the check condition was
reversed by mistake. Other similar calls that follow are being correctly
verified as failing. And, there were no checks of valid offset and
excessive length combinations that would cause the call to fail.

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

[-- Attachment #2: Type: text/html, Size: 3180 bytes --]

                 reply	other threads:[~2025-06-16 14:41 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-1724-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).