From: Filipe David Borba Manana <fdmanana@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Filipe David Borba Manana <fdmanana@gmail.com>
Subject: [PATCH] Btrfs-progs: Add missing free() against fs_info->super_copy
Date: Sat, 25 May 2013 14:49:51 +0100 [thread overview]
Message-ID: <1369489792-5673-1-git-send-email-fdmanana@gmail.com> (raw)
There was a missing free() call against fs_info->super_copy
in several places:
1) close_ctree()
2) open_ctree_broken() on failure
3) __open_ctree_fd() on failure
Filipe David Borba Manana (1):
Btrfs-progs: Add missing free() against fs_info->super_copy
btrfs-find-root.c | 4 ++--
disk-io.c | 5 +++--
2 files changed, 5 insertions(+), 4 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-05-25 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 13:49 Filipe David Borba Manana [this message]
2013-05-25 13:49 ` [PATCH] Btrfs-progs: Add missing free() against fs_info->super_copy Filipe David Borba Manana
-- strict thread matches above, loose matches on Subject: below --
2013-05-25 14:16 Filipe David Borba Manana
2013-05-25 14:16 ` Filipe David Borba Manana
2013-05-27 12:12 ` David Sterba
2013-05-27 12:31 ` Filipe David Manana
2013-05-27 15:32 ` David Sterba
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=1369489792-5673-1-git-send-email-fdmanana@gmail.com \
--to=fdmanana@gmail.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 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).