All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Ozor <tozor@jetfuelsoftware.com>
To: netfilter-devel@lists.netfilter.org
Subject: [PATCH 2.6.11.2 1/1] ipt_sctp chunk map definition too large
Date: Wed, 09 Mar 2005 15:25:15 -0600	[thread overview]
Message-ID: <422F69BB.3010301@jetfuelsoftware.com> (raw)

Greetings,

In the process of implementing a native Java iptables API, I discovered 
a bug in the ipt_sctp.h header file where the chunkmap is defined too 
large. This obviously does not affect execution, but will result in 
increased memory useage in libiptc, or in my case the java process.

	Tim Ozor (tozor@jetfuelsoftware.com)


diff -uprN linux-2.6.11.2.orig/include/linux/netfilter_ipv4/ipt_sctp.h 
linux-2.6.11.2/include/linux/netfilter_ipv4/ipt_sctp.h
--- linux-2.6.11.2.orig/include/linux/netfilter_ipv4/ipt_sctp.h 
2005-03-09 14:55:57.367211471 -0600
+++ linux-2.6.11.2/include/linux/netfilter_ipv4/ipt_sctp.h 
2005-03-09 14:57:21.203988675 -0600
@@ -22,7 +22,7 @@ struct ipt_sctp_info {
         u_int16_t dpts[2];  /* Min, Max */
         u_int16_t spts[2];  /* Min, Max */

-       u_int32_t chunkmap[256 / sizeof (u_int32_t)];  /* Bit mask of 
chunks to be matched according to RFC 2960 */
+       u_int32_t chunkmap[256 / (sizeof(u_int32_t)*8)];  /* Bit mask of 
chunks to be matched according to RFC 2960 */

  #define SCTP_CHUNK_MATCH_ANY   0x01  /* Match if any of the chunk 
types are present */
  #define SCTP_CHUNK_MATCH_ALL   0x02  /* Match if all of the chunk 
types are present */

             reply	other threads:[~2005-03-09 21:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 21:25 Tim Ozor [this message]
2005-03-09 21:30 ` [PATCH 2.6.11.2 1/1] ipt_sctp chunk map definition too large 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=422F69BB.3010301@jetfuelsoftware.com \
    --to=tozor@jetfuelsoftware.com \
    --cc=netfilter-devel@lists.netfilter.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.