From: "Morten Brørup" <mb@smartsharesystems.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbox@nvidia.com>,
Tomasz Duszynski <tduszynski@marvell.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org
Cc: "Morten Brørup" <mb@smartsharesystems.com>
Subject: [PATCH v3 0/3] handle sysconf(_SC_PAGESIZE) negative return value
Date: Tue, 24 Jun 2025 08:03:30 +0000 [thread overview]
Message-ID: <20250624080333.127618-1-mb@smartsharesystems.com> (raw)
In-Reply-To: <20250610131348.248800-1-mb@smartsharesystems.com>
Coverity reports some defects, where the root cause seems to be negative
return value from sysconf(_SC_PAGESIZE) not being handled.
This series addresses those defects in the DPDK libraries.
PS: "_SC_PAGESIZE" has the alias "_SC_PAGE_SIZE". Both are covered here.
Morten Brørup (3):
eal/unix: fix log message for madvise() failure
eal: handle sysconf(_SC_PAGESIZE) negative return value
pmu: handle sysconf(_SC_PAGESIZE) negative return value
lib/eal/freebsd/eal.c | 3 ++-
lib/eal/freebsd/eal_memory.c | 7 +++----
lib/eal/linux/eal.c | 3 ++-
lib/eal/unix/eal_unix_memory.c | 16 ++++++++++++++--
lib/pmu/pmu.c | 32 ++++++++++++++++++++++++++++++--
lib/vhost/vduse.c | 3 ++-
6 files changed, 53 insertions(+), 11 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2025-06-24 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 13:13 [PATCH] eal: handle sysconf() " Morten Brørup
2025-06-12 14:06 ` [PATCH v2] eal: handle sysconf(_SC_PAGESIZE) " Morten Brørup
2025-06-13 9:55 ` Burakov, Anatoly
2025-06-24 8:03 ` Morten Brørup [this message]
2025-06-24 8:03 ` [PATCH v3 1/3] eal/unix: fix log message for madvise() failure Morten Brørup
2025-06-24 8:03 ` [PATCH v3 2/3] eal: handle sysconf(_SC_PAGESIZE) negative return value Morten Brørup
2025-06-24 8:03 ` [PATCH v3 3/3] pmu: " Morten Brørup
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=20250624080333.127618-1-mb@smartsharesystems.com \
--to=mb@smartsharesystems.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.org \
--cc=tduszynski@marvell.com \
--cc=thomas@monjalon.net \
/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).