From: Kenji Okimoto <okimoto@clear-code.com>
To: linux-btrfs@vger.kernel.org
Cc: Kenji Okimoto <okimoto@clear-code.com>
Subject: [PATCH 0/3] btrfs-progs: fix problems reported by cppcheck
Date: Thu, 15 Nov 2012 13:47:49 +0900 [thread overview]
Message-ID: <1352954872-13770-1-git-send-email-okimoto@clear-code.com> (raw)
I fixed some problems reported by cppcheck:
[disk-io.c:462]: (error) Memory leak: log_root
[utils.c:983]: (error) Memory leak: fullpath
Patch set based on:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git#master
commit 91d9eec1ff044394f2b98ee7fcb76713dd33b994
Author: Chris Mason <chris.mason@fusionio.com>
Date: Thu Oct 4 20:35:31 2012 -0400
Kenji Okimoto (3):
btrfs-progs: plug a memory leak reported by cppcheck
btrfs-progs: check malloc() result
btrfs-progs: plug memory leaks in btrfs_scan_one_dir() reported by
cppcheck.
disk-io.c | 13 +++++++++++--
utils.c | 3 +++
2 files changed, 14 insertions(+), 2 deletions(-)
--
1.7.10.4
next reply other threads:[~2012-11-15 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 4:47 Kenji Okimoto [this message]
2012-11-15 4:47 ` [PATCH 1/3] btrfs-progs: plug a memory leak reported by cppcheck Kenji Okimoto
2012-11-15 4:47 ` [PATCH 2/3] btrfs-progs: check malloc() result Kenji Okimoto
2012-11-15 4:47 ` [PATCH 3/3] btrfs-progs: plug memory leaks in btrfs_scan_one_dir() reported by cppcheck Kenji Okimoto
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=1352954872-13770-1-git-send-email-okimoto@clear-code.com \
--to=okimoto@clear-code.com \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.