From: "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu>
To: netfilter-devel@vger.kernel.org, Jan Engelhardt <jengelh@inai.de>
Cc: Jaroslav Drzik <jaro@ttx.sk>, ipt_ACCOUNT@developer.intra2net.com
Subject: Re: xtables-addons 64-bit counter patch
Date: Sun, 8 Nov 2015 18:49:11 -0500 [thread overview]
Message-ID: <20151108184911.58e53fe5@playground> (raw)
In-Reply-To: <20151019013454.6f81f4f5@playground>
Re-sent, as the original may have been overlooked.
Neal
On Mon, 19 Oct 2015 01:34:54 -0400
"Neal P. Murphy" <neal.p.murphy@alum.wpi.edu> wrote:
> On Sat, 6 Jun 2015 13:15:38 +0200 (CEST)
> Jan Engelhardt <jengelh@inai.de> wrote:
>
> > x
> > On Friday 2015-06-05 00:04, Neal P. Murphy wrote:
> > >The theory:
> > > - Use two kernel pages for the counters for each group of 256
> > > addresses.
> > > - Change counters to 64-bit.
> > > - Change to __get_free_pages/free_pages, using order=2 (two
> > > consecutive pages), and zero both pages.
> > > - Change "%u" to "%llu" as needed.
> > > - Everything else pretty much stays the same.
> > >
> > >I also changed tmpbuf to two pages (Justin Case's idea), but I
> > >don't know if that's really necessary.
> > >
> > >Did I miss anything?
> >
> > I applied it.
>
> Disembowel me with a wooden spoon. My first patch makes xt_ACCOUNT hiss. Well, I think that's what a memory leak sounds like.
>
> Below is the patch with the *rest* of the free_page(X) calls changed to free_pages(X, 2). xt_ACCOUNT should always allocate memory in page pairs. And always *free* memory in page pairs.
>
> Neal
>
> --------
diff -Nubr xtables-addons-1.45-P1/extensions/ACCOUNT/xt_ACCOUNT.c xtables-addons-1.45/extensions/ACCOUNT/xt_ACCOUNT.c
--- xtables-addons-1.45-P1/extensions/ACCOUNT/xt_ACCOUNT.c 2015-10-19 01:23:03.000000000 -0400
+++ xtables-addons-1.45/extensions/ACCOUNT/xt_ACCOUNT.c 2015-10-19 01:23:39.000000000 -0400
@@ -145,7 +145,7 @@
unsigned int b;
for (b = 0; b <= 255; b++) {
if (mask_16->mask_24[b]) {
- free_page((unsigned long)mask_16->mask_24[b]);
+ free_pages((unsigned long)mask_16->mask_24[b], 2);
}
}
free_pages((unsigned long)data, 2);
@@ -162,10 +162,10 @@
for (b = 0; b <= 255; b++) {
if (mask_16->mask_24[b]) {
- free_page((unsigned long)mask_16->mask_24[b]);
+ free_pages((unsigned long)mask_16->mask_24[b], 2);
}
}
- free_page((unsigned long)mask_16);
+ free_pages((unsigned long)mask_16, 2);
}
}
free_pages((unsigned long)data, 2);
next prev parent reply other threads:[~2015-11-08 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 22:04 xtables-addons 64-bit counter patch Neal P. Murphy
2015-06-06 11:15 ` Jan Engelhardt
2015-06-07 5:21 ` Neal P. Murphy
2015-10-19 5:34 ` Neal P. Murphy
2015-11-08 23:49 ` Neal P. Murphy [this message]
2015-11-09 9:14 ` Jan Engelhardt
2015-11-09 21:34 ` Jan Engelhardt
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=20151108184911.58e53fe5@playground \
--to=neal.p.murphy@alum.wpi.edu \
--cc=ipt_ACCOUNT@developer.intra2net.com \
--cc=jaro@ttx.sk \
--cc=jengelh@inai.de \
--cc=netfilter-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.