All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deti Fliegl <deti@fliegl.de>
To: Pablo Neira <pablo@eurodev.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: again: conntrack & 2.6.14-git11
Date: Fri, 11 Nov 2005 08:10:53 +0100	[thread overview]
Message-ID: <437443FD.1060604@fliegl.de> (raw)
In-Reply-To: <4371FBDD.4020302@eurodev.net>

Pablo Neira wrote:
> I don't see the patch that is supposed to fix the problem in that git
> snapshot. Please, make sure that the patch attached is applied to your
> kernel tree.
Had a defective harddisk on my testsystem and was not able to test 
yesterday. Now I tried git13 which incorporates this patch but still got 
an oops. Not sure, if this is related to netlink/conntrack.

wget[4709]: segfault at 00002aab1313321d rip 00002aaaab21ba6f rsp 
00007fffffb61510 error 4
ACCEPT IN=mgmt OUT= MAC=00:04:23:b7:70:7c:00:d0:03:49:58:00:08:00 
SRC=10.156.10.105 DST=XX LEN=84 TOS=0x00 PREC=0x00 TTL=63 ID=2630 
PROTO=ICMP TYPE=0 CODE=0
  ID=55676 SEQ=1
Badness in __kfree_skb at net/core/skbuff.c:334

Call Trace:<ffffffff80271ab7>{__kfree_skb+165} 
<ffffffff80287fb5>{netlink_recvmsg+259}
        <ffffffff8026c14d>{sock_recvmsg+284} 
<ffffffff802e20eb>{thread_return+0}
        <ffffffff80151ca7>{file_read_actor+0} 
<ffffffff80143021>{autoremove_wake_function+0}
        <ffffffff8026d648>{sys_recvmsg+357} 
<ffffffff80143021>{autoremove_wake_function+0}
        <ffffffff8017c6d6>{pipe_writev+1293} 
<ffffffff80170cbe>{vfs_write+326}
        <ffffffff80170db2>{sys_write+69} <ffffffff8010d94e>{system_call+126}

Badness in __kfree_skb at net/core/skbuff.c:334

Call Trace:<ffffffff80271ab7>{__kfree_skb+165} 
<ffffffff80287fb5>{netlink_recvmsg+259}
        <ffffffff8026c14d>{sock_recvmsg+284} 
<ffffffff802e20eb>{thread_return+0}
        <ffffffff80151ca7>{file_read_actor+0} 
<ffffffff80143021>{autoremove_wake_function+0}
        <ffffffff8026d648>{sys_recvmsg+357} 
<ffffffff8017c6d6>{pipe_writev+1293}
        <ffffffff80170cbe>{vfs_write+326} <ffffffff80170db2>{sys_write+69}
        <ffffffff8010d94e>{system_call+126}
scheduling while atomic: conntrack/0xffffff00/15404

Call Trace:<ffffffff802e12af>{schedule+126} 
<ffffffff80170cbe>{vfs_write+326}
        <ffffffff80170db2>{sys_write+69} 
<ffffffff8010d9b8>{sysret_careful+13}

Further tried the refcount patch with 2.6.14 (no git version) without 
success (oops).

      reply	other threads:[~2005-11-11  7:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09 10:58 again: conntrack & 2.6.14-git11 Deti Fliegl
2005-11-09 13:38 ` Pablo Neira
2005-11-11  7:10   ` Deti Fliegl [this message]

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=437443FD.1060604@fliegl.de \
    --to=deti@fliegl.de \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@eurodev.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.