From: Mark Tinguely <tinguely@sgi.com>
To: xfs@oss.sgi.com
Subject: [PATCH] xfs: fix memory leak in xfs_dir2_node_removename
Date: Fri, 27 Sep 2013 08:01:31 -0500 [thread overview]
Message-ID: <20130927130140.640252809@sgi.com> (raw)
[-- Attachment #1: xfs-fix-leak-in-xfs_dir2_node_removename.patch --]
[-- Type: text/plain, Size: 1328 bytes --]
Free the memory pointed to by state before returning on error from
xfs_dir2_node_removename.c
Signed-off-by: Mark Tinguely <tinguely@sgi.com>
---
Found by Coverity (134681) in userspace, same patch applies there
also.
fs/xfs/xfs_dir2_node.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
Index: b/fs/xfs/xfs_dir2_node.c
===================================================================
--- a/fs/xfs/xfs_dir2_node.c
+++ b/fs/xfs/xfs_dir2_node.c
@@ -2131,10 +2131,9 @@ xfs_dir2_node_removename(
/*
* Didn't find it, upper layer screwed up.
*/
- if (rval != EEXIST) {
- xfs_da_state_free(state);
- return rval;
- }
+ if (rval != EEXIST)
+ goto done;
+
blk = &state->path.blk[state->path.active - 1];
ASSERT(blk->magic == XFS_DIR2_LEAFN_MAGIC);
ASSERT(state->extravalid);
@@ -2145,7 +2144,7 @@ xfs_dir2_node_removename(
error = xfs_dir2_leafn_remove(args, blk->bp, blk->index,
&state->extrablk, &rval);
if (error)
- return error;
+ goto done;
/*
* Fix the hash values up the btree.
*/
@@ -2160,6 +2159,7 @@ xfs_dir2_node_removename(
*/
if (!error)
error = xfs_dir2_node_to_leaf(state);
+done:
xfs_da_state_free(state);
return error;
}
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-09-27 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 13:01 Mark Tinguely [this message]
2013-09-27 13:08 ` [PATCH] xfs: fix memory leak in xfs_dir2_node_removename Carlos Maiolino
2013-09-27 16:44 ` Eric Sandeen
2013-09-27 17:48 ` Mark Tinguely
2013-09-27 17:55 ` Eric Sandeen
2013-09-27 19:36 ` Roger Willcocks
2013-09-27 19:52 ` Mark Tinguely
2013-09-27 20:04 ` Eric Sandeen
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=20130927130140.640252809@sgi.com \
--to=tinguely@sgi.com \
--cc=xfs@oss.sgi.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