From mboxrd@z Thu Jan 1 00:00:00 1970 From: Deti Fliegl Subject: Re: Unknown Attribute 5/conntrack -L Date: Mon, 31 Oct 2005 21:36:38 +0100 Message-ID: <43668056.8000400@fliegl.de> References: <43662D1E.4000308@eurodev.net> <200510311902.j9VJ28fq026612@toshiba.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: pablo@eurodev.net, netfilter-devel@lists.netfilter.org Return-path: To: Yasuyuki KOZAKAI In-Reply-To: <200510311902.j9VJ28fq026612@toshiba.co.jp> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org Hi Yasuyuki, > I'm not sure it's the reason of oops, but at least attached patch fixes > double free after netlink_unicast(). Krzysztof, could you try this ? Tried it with 2.6.14 - after 20 minutes of calling conntrack -L in an endless loop (with ~20000 entries and 800Mbit/s load) it happened again: <4>Badness in __kfree_skb at net/core/skbuff.c:330 <4> <4>Call Trace:{__kfree_skb+167} {netlink_recvmsg+279} <4> {sock_recvmsg+315} {update_atime+151} <4> {do_generic_mapping_read+1098} {buffered_rmqueue+529} <4> {activate_task+149} {try_to_wake_up+1083} <4> {autoremove_wake_function+0} {sys_recvmsg+395} <4> {pipe_writev+1319} {vfs_write+344} <4> {sys_write+83} {system_call+126} <4> <4>Badness in __kfree_skb at net/core/skbuff.c:330 <4> <4>Call Trace:{__kfree_skb+167} {netlink_recvmsg+279} <4> {sock_recvmsg+315} {update_atime+151} <4> {do_generic_mapping_read+1098} {buffered_rmqueue+529} <4> {activate_task+149} {try_to_wake_up+1083} <4> {autoremove_wake_function+0} {sys_recvmsg+395} <4> {pipe_writev+1319} {vfs_write+344} <4> {sys_write+83} {system_call+126} <4> <4>Badness in __kfree_skb at net/core/skbuff.c:330 <4> <4>Call Trace:{__kfree_skb+167} {netlink_recvmsg+279} <4> {sock_recvmsg+315} {update_atime+151} <4> {do_generic_mapping_read+1098} {buffered_rmqueue+529} <4> {activate_task+149} {try_to_wake_up+1083} <4> {autoremove_wake_function+0} {sys_recvmsg+395} <4> {pipe_writev+1319} {vfs_write+344} <4> {sys_write+83} {system_call+126} <4> <3>scheduling while atomic: conntrack/0xffffff00/32033 <4> <4>Call Trace:{schedule+125} {vfs_write+344} <4> {sys_write+83} {sysret_careful+13} <4> > I don't think so. Deti reports similer oops on 2.6.14 which has been already > out, so this should be fixed asap. good idea. Deti