From: Jim Meyering <jim@meyering.net>
To: linux-btrfs@vger.kernel.org
Subject: disk-io.c (open_ctree): avoid leaks
Date: Tue, 09 Sep 2008 16:40:28 +0200 [thread overview]
Message-ID: <87y7211ixv.fsf@rho.meyering.net> (raw)
These two variables (chunk_root and dev_root) that were not
tested for failed allocation weren't freed-upon-failure either:
changeset: 709:c40da2ab8c03
tag: tip
user: Jim Meyering <meyering@redhat.com>
date: Tue Sep 09 16:35:47 2008 +0200
files: disk-io.c
description:
disk-io.c (open_ctree): avoid leaks
diff --git a/disk-io.c b/disk-io.c
--- a/disk-io.c
+++ b/disk-io.c
@@ -1655,6 +1655,8 @@
bdi_destroy(&fs_info->bdi);
#endif
kfree(fs_info);
+ kfree(chunk_root);
+ kfree(dev_root);
return ERR_PTR(err);
}
reply other threads:[~2008-09-09 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87y7211ixv.fsf@rho.meyering.net \
--to=jim@meyering.net \
--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