DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 2041] baseband/null: socket_id parsed two bytes wide
Date: Sun, 13 Sep 2026 17:38:07 +0000	[thread overview]
Message-ID: <bug-2041-3@https.bugs.dpdk.org/> (raw)

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

            Bug ID: 2041
           Summary: baseband/null: socket_id parsed two bytes wide
           Product: DPDK
           Version: 26.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

drivers/baseband/null/bbdev_null.c:207

parse_u16_arg() stores a uint16_t. It is used for queues_num, which is a
uint16_t, but also for socket_id:

        rte_kvargs_process(kvlist, ..., &parse_u16_arg, &params->socket_id);

where socket_id is an int, so only two of four bytes are written.

(The same file also has a range check which only tests the upper bound, so
a negative socket id is accepted -- that part is not a size bug.)

Fixes: 7dc2b1589440 ("bb/null: add null base band device driver")

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

                 reply	other threads:[~2026-09-13 17:38 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-2041-3@https.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