public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1871] idxd_dmadev.portal volatile usage
Date: Sun, 25 Jan 2026 21:17:23 +0000	[thread overview]
Message-ID: <bug-1871-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1871

            Bug ID: 1871
           Summary: idxd_dmadev.portal volatile usage
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: scott.k.mitch1@gmail.com
  Target Milestone: ---

idxd_dmadev_probe_pci uses RTE_PTR_ADD(idxd.u.pci->portals) [1] where the
argument is volatile [2] and assigns the result to idxd_dmadev.portal which is
not volatile [3]. Disqualifying quantifiers should be done explicitly if
desired (not implicitly through RTE_PTR_ADD) and clear comments added, or
qualifiers should be preserved.

[1]
https://github.com/DPDK/dpdk/commit/9449330a845868de810b1c41b4b8e72ad41e031e#diff-976cfc47c9f1dfe38582a76e3dafe1275c55e44af64c6573ea1674c8bd94c560R260

[2]
https://github.com/DPDK/dpdk/commit/9449330a845868de810b1c41b4b8e72ad41e031e#diff-54e4d0d3f90a1a90e85160d1cd74aba322b2ed5743eed090fa00028fdbf70539R39

[3]
https://github.com/DPDK/dpdk/commit/e888bb1278c6c72f1bef774f14a9ee4836265624#diff-54e4d0d3f90a1a90e85160d1cd74aba322b2ed5743eed090fa00028fdbf70539R40

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

             reply	other threads:[~2026-01-25 21:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-25 21:17 bugzilla [this message]
2026-02-17 22:03 ` [DPDK/other Bug 1871] idxd_dmadev.portal volatile usage bugzilla

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-1871-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