From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Horman Subject: Re: [patch] netfilter: default to NF_DROP in sip_help_tcp() Date: Wed, 4 Aug 2010 17:07:43 +0900 Message-ID: <20100804080742.GC10740@verge.net.au> References: <20100710031604.GA26990@verge.net.au> <4C3DAC25.3050401@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org To: Patrick McHardy Return-path: Received: from kirsty.vergenet.net ([202.4.237.240]:59253 "EHLO kirsty.vergenet.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752512Ab0HDIHu (ORCPT ); Wed, 4 Aug 2010 04:07:50 -0400 Content-Disposition: inline In-Reply-To: <4C3DAC25.3050401@trash.net> Sender: netfilter-devel-owner@vger.kernel.org List-ID: On Wed, Jul 14, 2010 at 02:23:01PM +0200, Patrick McHardy wrote: > On 10.07.2010 05:16, Simon Horman wrote: > > I initially noticed this because of the compiler warning below, but it does > > seem to be a valid concern in the case where ct_sip_get_header() returns 0 > > in the first iteration of the while loop. > > > > net/netfilter/nf_conntrack_sip.c: In function 'sip_help_tcp': > > net/netfilter/nf_conntrack_sip.c:1379: warning: 'ret' may be used uninitialized in this function > > Thanks Simon. I've applied the patch, but changed NF_DROP to > NF_ACCEPT since we should avoid dropping packets with unknown > contents (not SIP) if possible. Hi Patrick, I'm not seeing this patch in nf-next-2.6. Am I looking in the wrong place?