From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Horman Subject: Re: [patch v2.3 3/4] IPVS: make FTP work with full NAT support Date: Sat, 10 Jul 2010 10:54:21 +0900 Message-ID: <20100710015420.GK5443@verge.net.au> References: <20100704113246.562399500@vergenet.net> <20100704114808.932594876@vergenet.net> <4C3316F0.2030807@trash.net> <20100707065324.GC20424@verge.net.au> <4C373F48.8080504@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org, Malcolm Turnbull , Wensong Zhang , Julius Volz , "David S. Miller" , Hannes Eder To: Patrick McHardy Return-path: Content-Disposition: inline In-Reply-To: <4C373F48.8080504@trash.net> Sender: lvs-devel-owner@vger.kernel.org List-Id: netfilter-devel.vger.kernel.org On Fri, Jul 09, 2010 at 05:24:56PM +0200, Patrick McHardy wrote: > Am 07.07.2010 08:53, schrieb Simon Horman: > > On Tue, Jul 06, 2010 at 01:43:44PM +0200, Patrick McHardy wrote: > >> Simon Horman wrote: > >>> @@ -219,19 +358,23 @@ static int ip_vs_ftp_out(struct ip_vs_ap > >>> buf_len = strlen(buf); > >>> + ct = nf_ct_get(skb, &ctinfo); > >>> + ret = nf_nat_mangle_tcp_packet(skb, > >>> + ct, > >>> + ctinfo, > >>> + start-data, > >>> + end-start, > >>> + buf, > >>> + buf_len); > >>> + > >>> + if (ct && ct != &nf_conntrack_untracked) > >> This does not make sense, you're already using the conntrack above > >> in the call to nf_nat_mangle_tcp_packet(), so the check should > >> probably happen before that. You also should be checking the > >> return value of nf_nat_mangle_tcp_packet() before setting up the > >> expectation. > >> > >>> + ip_vs_expect_related(skb, ct, n_cp, > >>> + IPPROTO_TCP, NULL, 0); > > > > Good point. Is this better? > > > > ct = nf_ct_get(skb, &ctinfo); > > if (ct && !nf_ct_is_untracked()) { > > ret = nf_nat_mangle_tcp_packet(skb, ct, ctinfo, > > start-data, end-start, > > buf, buf_len); > > if (ret) > > ip_vs_expect_related(skb, ct, n_cp, > > IPPROTO_TCP, NULL, 0); > > Yes, that's better, although we're usually dropping packets > when mangling fails. This can only happen under memory pressure, > the assumption is that we might be able to properly mangle > the packet when it is retransmitted. I didn't notice this either, but ret will be end up being the return value of ip_vs_ftp_out(), and if that is zero the packet will be dropped.