From: alison.schofield@intel.com
To: nvdimm@lists.linux.dev
Cc: Alison Schofield <alison.schofield@intel.com>
Subject: [ndctl PATCH 0/5] Address Coverity Scan Defects
Date: Mon, 3 Mar 2025 16:37:06 -0800 [thread overview]
Message-ID: <cover.1741047738.git.alison.schofield@intel.com> (raw)
From: Alison Schofield <alison.schofield@intel.com>
The NDCTL project routinely addresses any and all coverity defects
before each release. This new set of reports suggests enhancements
to the scan capabilities since none of this code has been touched
recently. Game on, we we'll squash 'em!
Alison Schofield (5):
ndctl/namespace: avoid integer overflow in namespace validation
ndctl/namespace: close file descriptor in do_xaction_namespace()
ndctl/dimm: do not increment a ULLONG_MAX slot value
ndctl/namespace: protect against overflow handling param.offset
ndctl/namespace: protect against under|over-flow w bad param.align
ndctl/dimm.c | 8 +++++---
ndctl/namespace.c | 37 ++++++++++++++++++++++++++++---------
2 files changed, 33 insertions(+), 12 deletions(-)
base-commit: d2c55938a0c7308cba07cb23b598df1be93f1d38
--
2.37.3
next reply other threads:[~2025-03-04 0:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 0:37 alison.schofield [this message]
2025-03-04 0:37 ` [ndctl PATCH 1/5] ndctl/namespace: avoid integer overflow in namespace validation alison.schofield
2025-03-05 16:24 ` Dave Jiang
2025-03-04 0:37 ` [ndctl PATCH 2/5] ndctl/namespace: close file descriptor in do_xaction_namespace() alison.schofield
2025-03-05 16:32 ` Dave Jiang
2025-03-04 0:37 ` [ndctl PATCH 3/5] ndctl/dimm: do not increment a ULLONG_MAX slot value alison.schofield
2025-03-05 16:38 ` Dave Jiang
2025-03-06 22:56 ` Alison Schofield
2025-03-04 0:37 ` [ndctl PATCH 4/5] ndctl/namespace: protect against overflow handling param.offset alison.schofield
2025-03-05 16:43 ` Dave Jiang
2025-03-04 0:37 ` [ndctl PATCH 5/5] ndctl/namespace: protect against under|over-flow w bad param.align alison.schofield
2025-03-05 16:43 ` Dave Jiang
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=cover.1741047738.git.alison.schofield@intel.com \
--to=alison.schofield@intel.com \
--cc=nvdimm@lists.linux.dev \
/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).