From: Akinobu Mita <akinobu.mita@gmail.com>
To: hail-devel@vger.kernel.org
Cc: Akinobu Mita <akinobu.mita@gmail.com>
Subject: [PATCH] chunkd: fix duplicate stc_object allocation in stc_parse_key()
Date: Tue, 16 Mar 2010 18:59:29 +0900 [thread overview]
Message-ID: <1268733569-2306-1-git-send-email-akinobu.mita@gmail.com> (raw)
At the beginning of stc_parse_key(), st_object is allocated twice for
the same variable.
Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
---
lib/chunkdc.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lib/chunkdc.c b/lib/chunkdc.c
index 2696a81..67c39eb 100644
--- a/lib/chunkdc.c
+++ b/lib/chunkdc.c
@@ -831,7 +831,7 @@ void stc_free_keylist(struct st_keylist *keylist)
static void stc_parse_key(xmlDocPtr doc, xmlNode *node,
struct st_keylist *keylist)
{
- struct st_object *obj = calloc(1, sizeof(*obj));
+ struct st_object *obj;
xmlChar *xs;
obj = calloc(1, sizeof(*obj));
--
1.6.5.5
next reply other threads:[~2010-03-16 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 9:59 Akinobu Mita [this message]
2010-03-16 16:17 ` [PATCH] chunkd: fix duplicate stc_object allocation in stc_parse_key() Jeff Garzik
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=1268733569-2306-1-git-send-email-akinobu.mita@gmail.com \
--to=akinobu.mita@gmail.com \
--cc=hail-devel@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 read-only IMAP folder(s) and NNTP newsgroup(s).