From: NeilBrown <neilb@suse.de>
To: Jes.Sorensen@redhat.com
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 00/11] Memory/resource leaks and unchecked return fixes
Date: Tue, 1 Nov 2011 14:57:15 +1100 [thread overview]
Message-ID: <20111101145715.2229e964@notabene.brown> (raw)
In-Reply-To: <1320069759-13361-1-git-send-email-Jes.Sorensen@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Mon, 31 Oct 2011 15:02:28 +0100 Jes.Sorensen@redhat.com wrote:
> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>
> Hi,
>
> This is another pile of patches to fixup memory leaks and buffer
> overflows found in the coverity run.
Thanks Jes,
I have applied all of these.
NeilBrown
>
> Cheers,
> Jes
>
>
> Jes Sorensen (11):
> Fix memory leaks in reshape_array()
> Fix memory leak
> Fix memory leak
> Fix memory leak of 'st3' in array_try_spare()
> partition_try_spare() use closedir() to release DIR * returned by
> opendir()
> Fix memory leak
> Add missing return in case of trying to grow sub-array
> Avoid memory leak
> policy_add(): Add missing va_end()
> Write_rules(): Avoid stack corruption if using extremely long udev
> pathname
> mdmon(): Error out if failing to connect to victim monitor
>
> Assemble.c | 1 +
> Detail.c | 1 +
> Grow.c | 16 ++++++++++++++--
> Incremental.c | 6 +++++-
> mdmon.c | 8 +++++++-
> policy.c | 4 +++-
> super-gpt.c | 4 +++-
> super-intel.c | 1 +
> 8 files changed, 35 insertions(+), 6 deletions(-)
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2011-11-01 3:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 14:02 [PATCH 00/11] Memory/resource leaks and unchecked return fixes Jes.Sorensen
2011-10-31 14:02 ` [PATCH 01/11] Fix memory leaks in reshape_array() Jes.Sorensen
2011-10-31 14:02 ` [PATCH 02/11] Fix memory leak Jes.Sorensen
2011-10-31 14:02 ` [PATCH 03/11] " Jes.Sorensen
2011-10-31 14:02 ` [PATCH 04/11] Fix memory leak of 'st3' in array_try_spare() Jes.Sorensen
2011-10-31 14:02 ` [PATCH 05/11] partition_try_spare() use closedir() to release DIR * returned by opendir() Jes.Sorensen
2011-10-31 14:02 ` [PATCH 06/11] Fix memory leak Jes.Sorensen
2011-10-31 14:02 ` [PATCH 07/11] Add missing return in case of trying to grow sub-array Jes.Sorensen
2011-10-31 14:02 ` [PATCH 08/11] Avoid memory leak Jes.Sorensen
2011-10-31 14:02 ` [PATCH 09/11] policy_add(): Add missing va_end() Jes.Sorensen
2011-10-31 14:02 ` [PATCH 10/11] Write_rules(): Avoid stack corruption if using extremely long udev pathname Jes.Sorensen
2011-10-31 14:02 ` [PATCH 11/11] mdmon(): Error out if failing to connect to victim monitor Jes.Sorensen
2011-11-01 3:57 ` NeilBrown [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=20111101145715.2229e964@notabene.brown \
--to=neilb@suse.de \
--cc=Jes.Sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
/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).