public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Martin Clausen <martin@ostenfeld.dk>
Cc: netfilter-devel@lists.samba.org, linux-kernel@vger.kernel.org
Subject: Re: Kernel Oops when using the Netfilter QUEUE target
Date: Thu, 26 Apr 2001 13:13:20 +1000	[thread overview]
Message-ID: <13257.988254800@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 24 Apr 2001 19:25:47 +0200." <20010424192547.B2840@ostenfeld.dk>

On Tue, 24 Apr 2001 19:25:47 +0200, 
Martin Clausen <martin@ostenfeld.dk> wrote:
>I have encountered a problem (perhaps a bug)! The attached code makes my kernel oops
>in some cases when injecting new packets through Netfilter's QUEUE target. The problem 
>Entering kdb (current=0xc68f6000, pid 884) Oops: Oops                         
>due to oops @ 0xc01e7456                                                      
>eax = 0x000005dc ebx = 0xc7acf224 ecx = 0x0000000e edx = 0xc72f8440           
>esi = 0xc7cee740 edi = 0x00000000 esp = 0xc68f7c90 eip = 0xc01e7456           
>ebp = 0xc68f7cb0 xss = 0x00000018 xcs = 0x00000010 eflags = 0x00010287        
>xds = 0x00000018 xes = 0x00000018 origeax = 0xffffffff &regs = 0xc68f7c5c     
>kdb> 
>
>I will be glad to submit som more (debug) information?!

At the very least, you need to run the kdb commands 'bt' (backtrace)
and 'id %eip-0x10' (disassemble around failing instruction).  Registers
and eip on their own are almost meaningless.

ps. Don't copy me on the reply, I only maintain kdb, not the failing
    netfilter code.

  reply	other threads:[~2001-04-26  3:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 17:25 Kernel Oops when using the Netfilter QUEUE target Martin Clausen
2001-04-26  3:13 ` Keith Owens [this message]
     [not found] <20010425004937.A3904@ostenfeld.dk>
2001-04-25  6:24 ` James Morris
2001-04-26 22:48   ` Martin Clausen
2001-04-27 13:42     ` Rusty Russell

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=13257.988254800@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@ostenfeld.dk \
    --cc=netfilter-devel@lists.samba.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox