NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: jmoyer@redhat.com
To: nvdimm@lists.linux.dev
Cc: vishal.l.verma@intel.com, Jeff Moyer <jmoyer@redhat.com>
Subject: [PATCH ndctl 0/2] fix errors pointed out by static analysis
Date: Fri,  3 May 2024 16:54:54 -0400	[thread overview]
Message-ID: <20240503205456.80004-1-jmoyer@redhat.com> (raw)

From: Jeff Moyer <jmoyer@redhat.com>

This series fixes a couple of minor issues flagged by coverity.

Jeff Moyer (2):
  ndctl/keys.c: don't leak fd in error cases
  libndctl.c: major and minor numbers are unsigned

 ndctl/keys.c         | 16 ++++++++--------
 ndctl/lib/libndctl.c |  7 ++++---
 2 files changed, 12 insertions(+), 11 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-05-03 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 20:54 jmoyer [this message]
2024-05-03 20:54 ` [PATCH ndctl 1/2] ndctl/keys.c: don't leak fd in error cases jmoyer
2024-05-06 19:11   ` Verma, Vishal L
2024-05-03 20:54 ` [PATCH ndctl 2/2] libndctl.c: major and minor numbers are unsigned jmoyer
2024-05-06 19:11   ` Verma, Vishal L

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=20240503205456.80004-1-jmoyer@redhat.com \
    --to=jmoyer@redhat.com \
    --cc=nvdimm@lists.linux.dev \
    --cc=vishal.l.verma@intel.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).