All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jingmin Zhou <zhouji@cs.ucdavis.edu>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: double-free bug and a question
Date: Fri, 15 Sep 2006 06:24:50 +0200	[thread overview]
Message-ID: <450A2B12.4010503@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0609141621400.27445@mariner.cs.ucdavis.edu>

jmzhou.ml@gmail.com wrote:
> Apology if this has been reported. Here's the way to reproduce the crash:
> 
> # iptables -A INPUT --protocol udp -m multiport --dports 65530:65535 -m
> multiport --sport 53:67 -j ACCEPT
> *** glibc detected *** double free or corruption (!prev): 0x08055160 ***
> Abort (core dumped)
> 
> # iptables -A INPUT --protocol udp -m multiport --dports 65530:65535 -m
> multiport --sports 53:67 -j ACCEPT
> Bad argument `53:67'
> Try `iptables -h' or 'iptables --help' for more information.
> 
> $ iptables --version
> iptables v1.3.5
> 
> 
> What I want to do is to define multiple ports for both source and
> destination in a single iptables rule. Is there any way to do it?
> Thanks!

Read the help for multiport, the ports are given as comma-seperated
list. For simple ranges you don't need multiport. For source and
destination you must only specify "-m multiport" once.

I have no idea where the crash comes from (works fine here). Please
try to get a backtrace by running the command in gdb:

gdb iptables

(gdb) run -A INPUT ...
<crash>
(gdb) backtrace

  reply	other threads:[~2006-09-15  4:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 23:29 double-free bug and a question jmzhou.ml
2006-09-15  4:24 ` Patrick McHardy [this message]
2006-09-15 17:35   ` jmzhou.ml
2006-09-15 21:05     ` Patrick McHardy

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=450A2B12.4010503@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=zhouji@cs.ucdavis.edu \
    /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.