From: Ariel Otilibili <ariel.otilibili@6wind.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>,
stable@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
Reshma Pattan <reshma.pattan@intel.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Ariel Otilibili <ariel.otilibili@6wind.com>
Subject: [PATCH v3 0/1] pcapng: fix null dereference in rte_pcapng_close
Date: Mon, 24 Feb 2025 17:40:30 +0100 [thread overview]
Message-ID: <20250224164031.587829-1-ariel.otilibili@6wind.com> (raw)
In-Reply-To: <20250216160833.3216001-1-ariel.otilibili@6wind.com>
Hello,
This patch addresses a warning found by static analysis; courtesy of Stephen Hemminger.
Thank you,
---
v3
* silently ignores NULL pointers (Stephen Hemminger)
* changed commit title
v2 (https://inbox.dpdk.org/dev/20250223214123.447579-1-ariel.otilibili@6wind.com/)
* rather change documentation than work around the bug (Stephen Hemminger)
* changed cover letter and commit message
v1 (https://inbox.dpdk.org/dev/20250216160833.3216001-1-ariel.otilibili@6wind.com/)
Ariel Otilibili (1):
pcapng: fix null dereference in rte_pcapng_close
.mailmap | 2 +-
lib/pcapng/rte_pcapng.c | 6 ++++--
2 files changed, 5 insertions(+), 3 deletions(-)
--
2.30.2
next prev parent reply other threads:[~2025-02-24 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 16:08 [PATCH " Ariel Otilibili
2025-02-16 16:08 ` [PATCH 1/1] " Ariel Otilibili
2025-02-16 16:51 ` Stephen Hemminger
2025-02-23 21:41 ` [PATCH v2 0/1] warn if NULL is passed to rte_pcapng_close Ariel Otilibili
2025-02-23 21:41 ` [PATCH v2 1/1] pcapng: " Ariel Otilibili
2025-02-23 22:04 ` Dmitry Kozlyuk
2025-02-24 15:42 ` Stephen Hemminger
2025-02-24 16:42 ` Ariel Otilibili
2025-02-24 16:40 ` Ariel Otilibili [this message]
2025-02-24 16:40 ` [PATCH v3 1/1] pcapng: fix null dereference in rte_pcapng_close Ariel Otilibili
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=20250224164031.587829-1-ariel.otilibili@6wind.com \
--to=ariel.otilibili@6wind.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=reshma.pattan@intel.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--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).