From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Netdev <netdev@vger.kernel.org>
Cc: hadi@cyberus.ca, Stephen Hemminger <shemminger@linux-foundation.org>
Subject: [PATCH] reset optind and fix memory leak in m_ipt/iptables target structure
Date: Thu, 7 Aug 2008 17:33:25 +0300 [thread overview]
Message-ID: <200808071733.26376.denys@visp.net.lb> (raw)
According iptables sources for reusing iptables target optind must be reset to
zero, this is important in batch processing. Also if we are using iptables
target, we are allocating memory for two temporary variables and inside
structure of iptables_target, which must be freed when job done. Also
tflags and used in structure must be reset, to zero for next reuse of
structure.
Signed-off-by: Denys Fedoryshchenko <denys@visp.net.lb>
Tested-by: Denys Fedoryshchenko <denys@visp.net.lb>
---
diff -Naur iproute2-original/tc/m_ipt.c iproute2-patched/tc/m_ipt.c
--- iproute2-original/tc/m_ipt.c 2008-08-05 19:15:56.000000000 +0000
+++ iproute2-patched/tc/m_ipt.c 2008-08-05 21:39:49.000000000 +0000
@@ -277,6 +277,8 @@
if (!handle) {
fputs(dlerror(), stderr);
printf("\n");
+ free(l_name);
+ free(new_name);
return NULL;
}
}
@@ -292,12 +294,16 @@
fputs(error, stderr);
fprintf(stderr, "\n");
dlclose(handle);
+ free(l_name);
+ free(new_name);
return NULL;
}
}
}
}
+ free(l_name);
+ free(new_name);
return m;
}
@@ -512,8 +518,15 @@
*argc_p = rargc - iargc;
*argv_p = argv;
- optind = 1;
+ optind = 0;
free_opts(opts);
+ /* Clear flags if target will be used again */
+ m->tflags=0;
+ m->used=0;
+ /* Free allocated memory */
+ if (m->t)
+ free(m->t);
+
return 0;
next reply other threads:[~2008-08-07 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 14:33 Denys Fedoryshchenko [this message]
2008-08-07 15:13 ` [PATCH] reset optind and fix memory leak in m_ipt/iptables target structure jamal
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=200808071733.26376.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).