From: Vinay Reddy <vinayvinay@gmail.com>
To: netfilter-devel@lists.netfilter.org
Subject: Kernel panic due to local out handler calling itself again.
Date: Fri, 25 Feb 2005 16:14:32 +0530 [thread overview]
Message-ID: <537f59d105022502444ad30394@mail.gmail.com> (raw)
Hi,
I am implementing a source routed protocol(like DSR) using netfilter
hooks. After rerouting the skb in my local_out handler, I return
NF_STOLEN and call the okfn (dst_output) directly. On testing the
code, we found that the local_out handler is being called, before the
previous call to local_out has returned. We were testing our protocol
by pinging.
In the first call of local_out, we get a normal echo packet(type 8),
but in the second call we get icmp packet types > 18 (NR_ICMP_TYPES).
We believe this caused the kernel panic that we observed. However, in
the oops trace the EIP value was 0x14000000, which we belive is not
pointing to our module. Infact in many of the dumps we observed, the
call trace did not contain any of our functions.
We are using the vanilla version of 2.6.10 kernel with
NF_DEBUG,KERNEL_DEBUG support enabled. Could this crash be due to the
fact that we are calling the okfn ourselves from local_out, which may
call a function thru the dst->output, which ultimately goes through
the LOCAL_OUT hook again, effectively we are somehow calling
ourselves.
But we are still not clear of the root of the problem we are facing.
We have been trying very hard to debug this problem, any help would be
greatly appreciated..
Thanks in advance.
Eagerly awaiting your reply.
Yours Sincerely,
Vinay Reddy.
reply other threads:[~2005-02-25 10:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=537f59d105022502444ad30394@mail.gmail.com \
--to=vinayvinay@gmail.com \
--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.