All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Vincent <cs83152@csie.chu.edu.tw>
Cc: 'Netfilter Development Mailinglist'
	<netfilter-devel@lists.netfilter.org>
Subject: Re: [kernel panic] iptables 1.2.7a + physdev patch
Date: Sat, 17 Sep 2005 21:33:24 +0200	[thread overview]
Message-ID: <432C6F84.90600@trash.net> (raw)
In-Reply-To: <000001c5baa6$f4bf1c70$aa0ba8c0@l7.com.tw>

Vincent wrote:
> Hello folks,
> 
> I have experiencend a kernel panic with iptables. Does anyone point any
> hints for me?
> Thanks in advance.
> 
> My Enviroment:
> Linux Kernel : 2.6.10
> Iptables: 1.2.7a
> 
> PS. I port the physdev patch from 1.2.9 back to 1.2.7a. Will this action
> cause kernel panic?

No, it shouldn't.

> Oops: 0000 [#1]
> SMP
> CPU:    0
> EIP:    0060:[<c025a966>]    Not tainted VLI
> EFLAGS: 00010246   (2.6.10)
> EIP is at target+0x24d/0x2ce

Unfortunately half the iptables targets use this name, so its hard to
tell which one it is. If this crash is reproducable you can find out
which module the function belongs to by comparing EIP with the output
of cat /proc/modules.

      reply	other threads:[~2005-09-17 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 10:10 [kernel panic] iptables 1.2.7a + physdev patch Vincent
2005-09-17 19:33 ` Patrick McHardy [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=432C6F84.90600@trash.net \
    --to=kaber@trash.net \
    --cc=cs83152@csie.chu.edu.tw \
    --cc=netfilter-devel@lists.netfilter.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 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.