From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Xiao Ni <xni@redhat.com>
Cc: ncroxon@redhat.com, linux-raid@vger.kernel.org
Subject: Re: [PATCH V4 00/14] mdadm: fix coverity issues
Date: Mon, 5 Aug 2024 11:20:14 +0200 [thread overview]
Message-ID: <20240805112014.0000632b@linux.intel.com> (raw)
In-Reply-To: <20240726071416.36759-1-xni@redhat.com>
On Fri, 26 Jul 2024 15:14:02 +0800
Xiao Ni <xni@redhat.com> wrote:
> V2: replace close with close_fd and use is_fd_valid
> V3: Fix errors reported by checkpatch
> V4:
> don't need check fd is valid before close_fd
> replace strcat with snprintf
> replace dev_name with dev_path_name
>
> Xiao Ni (14):
> mdadm/Grow: fix coverity issue CHECKED_RETURN
> mdadm/Grow: fix coverity issue RESOURCE_LEAK
> mdadm/Grow: fix coverity issue STRING_OVERFLOW
> mdadm/Incremental: fix coverity issues.
> mdadm/mdmon: fix coverity issue CHECKED_RETURN
> mdadm/mdmon: fix coverity issue RESOURCE_LEAK
> mdadm/mdopen: fix coverity issue CHECKED_RETURN
> mdadm/mdopen: fix coverity issue STRING_OVERFLOW
> mdadm/mdstat: fix coverity issue CHECKED_RETURN
> mdadm/super0: fix coverity issue CHECKED_RETURN and EVALUATION_ORDER
> mdadm/super1: fix coverity issue CHECKED_RETURN
> mdadm/super1: fix coverity issue DEADCODE
> mdadm/super1: fix coverity issue EVALUATION_ORDER
> mdadm/super1: fix coverity issue RESOURCE_LEAK
>
> Grow.c | 87 ++++++++++++++++++++++++++++++++++++++++-----------
> Incremental.c | 20 ++++++------
> mdmon.c | 20 +++++++++---
> mdopen.c | 8 +++--
> mdstat.c | 12 +++++--
> super0.c | 10 ++++--
> super1.c | 32 ++++++++++++++-----
> 7 files changed, 139 insertions(+), 50 deletions(-)
>
Applied!
Sorry for the delay. I was few days out of office!
Mariusz
prev parent reply other threads:[~2024-08-05 9:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 7:14 [PATCH V4 00/14] mdadm: fix coverity issues Xiao Ni
2024-07-26 7:14 ` [PATCH 01/14] mdadm/Grow: fix coverity issue CHECKED_RETURN Xiao Ni
2024-07-26 7:14 ` [PATCH 02/14] mdadm/Grow: fix coverity issue RESOURCE_LEAK Xiao Ni
2024-07-26 7:14 ` [PATCH 03/14] mdadm/Grow: fix coverity issue STRING_OVERFLOW Xiao Ni
2024-07-26 7:14 ` [PATCH 04/14] mdadm/Incremental: fix coverity issues Xiao Ni
2024-07-26 7:14 ` [PATCH 05/14] mdadm/mdmon: fix coverity issue CHECKED_RETURN Xiao Ni
2024-07-26 7:14 ` [PATCH 06/14] mdadm/mdmon: fix coverity issue RESOURCE_LEAK Xiao Ni
2024-07-26 7:14 ` [PATCH 07/14] mdadm/mdopen: fix coverity issue CHECKED_RETURN Xiao Ni
2024-07-26 7:14 ` [PATCH 08/14] mdadm/mdopen: fix coverity issue STRING_OVERFLOW Xiao Ni
2024-07-26 7:14 ` [PATCH 09/14] mdadm/mdstat: fix coverity issue CHECKED_RETURN Xiao Ni
2024-07-26 7:14 ` [PATCH 10/14] mdadm/super0: fix coverity issue CHECKED_RETURN and EVALUATION_ORDER Xiao Ni
2024-07-26 7:14 ` [PATCH 11/14] mdadm/super1: fix coverity issue CHECKED_RETURN Xiao Ni
2024-07-26 7:14 ` [PATCH 12/14] mdadm/super1: fix coverity issue DEADCODE Xiao Ni
2024-07-26 7:14 ` [PATCH 13/14] mdadm/super1: fix coverity issue EVALUATION_ORDER Xiao Ni
2024-07-26 7:14 ` [PATCH 14/14] mdadm/super1: fix coverity issue RESOURCE_LEAK Xiao Ni
2024-07-26 8:01 ` [PATCH V4 00/14] mdadm: fix coverity issues Paul Menzel
2024-07-30 13:51 ` Mariusz Tkaczyk
2024-08-05 9:20 ` Mariusz Tkaczyk [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=20240805112014.0000632b@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=ncroxon@redhat.com \
--cc=xni@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).