From: Pablo Neira <pablo@eurodev.net>
To: Nicolas Bouliane <nib@cookinglinux.org>
Cc: netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH] ip_conntrack_ftp segfault
Date: Tue, 04 Jan 2005 11:35:09 +0100 [thread overview]
Message-ID: <41DA715D.2080704@eurodev.net> (raw)
In-Reply-To: <41D99B6B.6050601@cookinglinux.org>
nice catch, but read the comments below.
Nicolas Bouliane wrote:
> This patch fix two bugs (when DEBUGP is defined):
> o The var `data` doesn't exist, hence gcc complains.
> o It segfault because we print an integer with `%s`.
>
>------------------------------------------------------------------------
>
>--- /usr/src/old/linux-2.6.10/net/ipv4/netfilter/ip_conntrack_ftp.c 2004-12-24 16:35:59.000000000 -0500
>+++ ip_conntrack_ftp.c 2005-01-03 14:09:06.000000000 -0500
>
>
this header must always look like, for example:
--- linux-2.6.10/net/ipv4/netfilter/ip_conntrack_ftp.c 2004-10-20
10:12:06 +02:00
+++ linux-2.6.10-nicolas/net/ipv4/netfilter/ip_conntrack_ftp.c
2005-01-02 16:09:01 +01:00
>@@ -347,9 +347,8 @@
> goto out;
> }
>
>- DEBUGP("conntrack_ftp: match `%.*s' (%u bytes at %u)\n",
>- (int)matchlen, data + matchoff,
>- matchlen, ntohl(th->seq) + matchoff);
>+ DEBUGP("conntrack_ftp: match `%s' (%u bytes at %u)\n",
>+ search[i].pattern, matchlen, ntohl(th->seq) + matchoff);
>
>
Since this is a minor fix, try to modify as less things as you can. data
doesn't exist but look for its natural replacement which is fb_ptr.
Rusty punish me yesterday to read part (11) of
Documentation/SubmittingPatches in the kernel source tree :). So do it
you as well and add your sign-off.
Resend a patch which fixes the things above. After that, let wait to see
if Patrick wants to add this to his changeset 8).
--
Pablo
next prev parent reply other threads:[~2005-01-04 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 19:22 [PATCH] ip_conntrack_ftp segfault Nicolas Bouliane
2005-01-04 10:35 ` Pablo Neira [this message]
2005-01-04 18:45 ` Nicolas Bouliane
2005-02-01 13:24 ` 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=41DA715D.2080704@eurodev.net \
--to=pablo@eurodev.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=nib@cookinglinux.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.