From: Stephen Hemminger <stephen@networkplumber.org>
To: NAGENDRA BALAGANI <nagendra.balagani@oracle.com>
Cc: "users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>,
Kapil Kumar Jain <kapil.k.jain@oracle.com>
Subject: Re: Clarification on Possible Buffer Overflow Issues Reported by Fortify Tool
Date: Thu, 5 Feb 2026 08:47:49 -0800 [thread overview]
Message-ID: <20260205084749.7ccb9e0f@phoenix.local> (raw)
In-Reply-To: <DM6PR10MB4124DC8DC85BFAE8FB7924D69699A@DM6PR10MB4124.namprd10.prod.outlook.com>
On Thu, 5 Feb 2026 06:58:29 +0000
NAGENDRA BALAGANI <nagendra.balagani@oracle.com> wrote:
> Hi Team,
> This is a gentle follow-up on my earlier mail regarding the Fortify static analysis findings in DPDK, for which I had also raised Bug 1748.
>
> Could you please let us know if there is any update or guidance from the community/maintainers on whether these are known false positives or if they need further investigation.
>
> Thank you for your time and support.
Did you file bugzilla entries and/or submit patches?
prev parent reply other threads:[~2026-02-05 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM6PR10MB41241F954D9C9680F98B29E996EFA@DM6PR10MB4124.namprd10.prod.outlook.com>
2026-02-05 6:58 ` Clarification on Possible Buffer Overflow Issues Reported by Fortify Tool NAGENDRA BALAGANI
2026-02-05 16:47 ` Stephen Hemminger [this message]
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=20260205084749.7ccb9e0f@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=kapil.k.jain@oracle.com \
--cc=nagendra.balagani@oracle.com \
--cc=users@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