From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pablo Neira Subject: Re: ip_ct_refresh lock issue Date: Sat, 28 Feb 2004 16:04:26 +0100 Sender: netfilter-devel-admin@lists.netfilter.org Message-ID: <4040ADFA.4030107@eurodev.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: To: Henrik Nordstrom , netfilter-devel@lists.netfilter.org In-Reply-To: Errors-To: netfilter-devel-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: netfilter-devel.vger.kernel.org Hi henrik, Henrik Nordstrom wrote: >But maybe there is some complication from NAT or related connections >requiring this locking? > > Actually a quick view at: http://lxr.linux.no/ident?v=2.6.1&i=ip_ct_refresh show me that this function is only called from conntrack related stuff, specifically from protocol and helpers, so i can't see that complication from NAT nor with related connections. Anyway, I'm not sure at all... that's why i need some feedback. >If not the lock should probably be moved down to the is_confirmed case. If >the connections is not yet confirmed then the only reference should be >from this packet (not yet in the hashes) and there should never be any >concurrent accesses. > > yes, this is exactly what i had in mind :-). thanks, Pablo