From: Patrick McHardy <kaber@trash.net>
To: Stephane Chazelas <stephane@artesyncp.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [bug+patch] SCTP and chunk types over 0x1f
Date: Mon, 25 Jun 2007 16:42:49 +0200 [thread overview]
Message-ID: <467FD469.8090001@trash.net> (raw)
In-Reply-To: <20070625141506.GX20467@artesyncp.com>
Stephane Chazelas wrote:
> On Mon, Jun 25, 2007 at 03:08:39PM +0100, Stephane Chazelas wrote:
>
>>>Does it stay completely compatible (modulo fixed bugs) then?
>>
>>AFAICT, yes (though I've not tested it). I don't know if the
>>kernel needs to be rebuilt for the bug to be fixed (that is, I
>>don't know whether in the kernel code there are some calls to
>>the SCTP_CHUNKMAP_IS_ALL_SET and cie macros with non-array
>>arguments, I don't think there are).
>
> [...]
>
> actually yes, the kernel is affected. See "return
> SCTP_CHUNKMAP_IS_CLEAR(chunkmap)" for instance in match_packet()
> in net/netfilter/xt_sctp.c, chunkmap is u_int32_t*, so
> ARRAY_SIZE(chunkmap) will return
> sizeof(u_int32_t*)/sizeof(u_int32_t) that is probably 1 or 2
> instead of 64 or 8.
>
> The fixed iptable should work with either a fixed or non-fixed
> kernel. However, with a non-fixed kernel, it will not fix the
> bug completely.
Thats fine, bugs in the kernel need a new kernel of course.
The important thing is that userspace compatibility of old
binaries is not affected. So the kernel just needs the
new xt_sctp file?
next prev parent reply other threads:[~2007-06-25 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 15:19 [bug+patch] SCTP and chunk types over 0x1f Stephane Chazelas
2007-06-25 13:40 ` Patrick McHardy
2007-06-25 13:50 ` Stephane Chazelas
2007-06-25 13:58 ` Patrick McHardy
2007-06-25 14:08 ` Stephane Chazelas
2007-06-25 14:15 ` Stephane Chazelas
2007-06-25 14:42 ` Patrick McHardy [this message]
2007-06-25 15:07 ` Stephane Chazelas
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=467FD469.8090001@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=stephane@artesyncp.com \
/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.