linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@RedHat.com>
To: Scott Mayhew <smayhew@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [nfs-utils PATCH 0/5] nfsdcld: Fix a number of Coverity Scan
Date: Fri, 17 Jul 2020 09:54:12 -0400	[thread overview]
Message-ID: <16bf22bf-d308-4f78-236e-2c11844a9aa1@RedHat.com> (raw)
In-Reply-To: <20200710203700.2546112-1-smayhew@redhat.com>



On 7/10/20 4:36 PM, Scott Mayhew wrote:
> These patches fix some errors in nfsdcld flagged by the Coverity scan
> software.
> 
> Scott Mayhew (5):
>   nfsdcld: Fix a few Coverity Scan RESOURCE_LEAK errors
>   nfsdcld: Fix a few Coverity Scan TOCTOU errors
>   nfsdcld: Fix a few Coverity Scan STRING_NULL errors
>   nfsdcld: Fix a few Coverity Scan CLANG_WARNING errors
>   nfsdcld: Fix a few Coverity Scan CHECKED_RETURN errors.
> 
>  utils/nfsdcld/legacy.c  | 38 ++++++++++++--------------------------
>  utils/nfsdcld/nfsdcld.c |  7 +++++--
>  utils/nfsdcld/sqlite.c  |  5 +++--
>  3 files changed, 20 insertions(+), 30 deletions(-)
> 
Committed... (tag: nfs-utils-2-5-2-rc2)

steved.


      parent reply	other threads:[~2020-07-17 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 20:36 [nfs-utils PATCH 0/5] nfsdcld: Fix a number of Coverity Scan Scott Mayhew
2020-07-10 20:36 ` [nfs-utils PATCH 1/5] nfsdcld: Fix a few Coverity Scan RESOURCE_LEAK errors Scott Mayhew
2020-07-10 20:36 ` [nfs-utils PATCH 2/5] nfsdcld: Fix a few Coverity Scan TOCTOU errors Scott Mayhew
2020-07-10 20:36 ` [nfs-utils PATCH 3/5] nfsdcld: Fix a few Coverity Scan STRING_NULL errors Scott Mayhew
2020-07-10 20:36 ` [nfs-utils PATCH 4/5] nfsdcld: Fix a few Coverity Scan CLANG_WARNING errors Scott Mayhew
2020-07-10 20:37 ` [nfs-utils PATCH 5/5] nfsdcld: Fix a few Coverity Scan CHECKED_RETURN errors Scott Mayhew
2020-07-17 13:54 ` Steve Dickson [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=16bf22bf-d308-4f78-236e-2c11844a9aa1@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=smayhew@redhat.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 NNTP newsgroup(s).