netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gao feng <gaofeng@cn.fujitsu.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org, xiaosuo@gmail.com
Subject: Re: Question about tcp reopen in tcp_in_window
Date: Thu, 17 Nov 2011 17:05:05 +0800	[thread overview]
Message-ID: <4EC4CE41.2060003@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1111170904040.27634@blackhole.kfki.hu>

于 2011年11月17日 16:07, Jozsef Kadlecsik 写道:
> No, the connection entry won't be destroyed by nf_ct_kill. Why do you 
> think so?
> 

Thanks Jozsef Kadlecsik.
nf_ct will be destroy when tcp_packet return -NF_REPEAT to nf_conntrack_in.
nf_conntrack_in will call nf_conntrack_put to destroy nf_conn
nf_conntrack_in:

	ret = l4proto->packet(ct, skb, dataoff, ctinfo, pf, hooknum);
        if (ret <= 0) {
                /* Invalid: inverse of the return code tells
                 * the netfilter core what to do */
                pr_debug("nf_conntrack_in: Can't track with proto module\n");
                nf_conntrack_put(skb->nfct);
                skb->nfct = NULL;
                NF_CT_STAT_INC_ATOMIC(net, invalid);
                if (ret == -NF_DROP)
                        NF_CT_STAT_INC_ATOMIC(net, drop);
                return -ret;
        }

I am wrong?
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-11-17  9:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17  6:52 Question about tcp reopen in tcp_in_window Gao feng
2011-11-17  8:07 ` Jozsef Kadlecsik
2011-11-17  9:05   ` Gao feng [this message]
2011-11-17  9:41     ` Jozsef Kadlecsik
2011-11-17 12:12       ` Gao feng

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=4EC4CE41.2060003@cn.fujitsu.com \
    --to=gaofeng@cn.fujitsu.com \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=xiaosuo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).