From: cranium2003 <cranium2003@yahoo.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org,
netfilter-devel@lists.netfilter.org, netdev@oss.sgi.com
Subject: Re: how netfilter handles fragmented packets
Date: Mon, 22 Nov 2004 22:07:10 -0800 (PST) [thread overview]
Message-ID: <20041123060710.35447.qmail@web41406.mail.yahoo.com> (raw)
In-Reply-To: <29495f1d04112211554e78da67@mail.gmail.com>
Hello Nish,
Thanks. I got it. dump_stack is implemented
in trap.c file in kernel source.
what i decide to use dump_stack is to do
pinging to myself at one console and same time call
dump_stack from user program. Is that right? But where
is output displayed? Dose that help me to find out
which function is called by output(skb).
regards,
cranium.
--- Nish Aravamudan <nish.aravamudan@gmail.com> wrote:
> On Sun, 21 Nov 2004 11:42:02 -0800 (PST),
> cranium2003
> <cranium2003@yahoo.com> wrote:
> >
> > --- Nish Aravamudan <nish.aravamudan@gmail.com>
> wrote:
> > Hello Nish,
> >
> >
> >
> > > On Sun, 21 Nov 2004 17:15:12 +0100 (MET), Jan
> > > Engelhardt
> > > <jengelh@linux01.gwdg.de> wrote:
> > > > >hello,
> > > > > In ip_output.c file ip_fragmet
> function
> > > when
> > > > >create a new fragmented packet given to
> > > output(skb)
> > > > >function. i want to know which function are
> > > actually
> > > > >called by output(skb)?
> > > >
> > > > use stack_dump() (or was it dump_stack()?)
> > >
> > > dump_stack(), if you want to dump the current
> > > process' stack context.
> > >
> > > -Nish
> > >
> >
> > can you please tell me how can i use dump_stack()
> > method? so using dump_stack i will come to know
> which
> > function will be called by output(skb) right? But
> > where i get dump_stack()???
>
> Last time i used it, I didn't need to do a darn
> thing. I believe it's
> part of the traps code, so you can just call
> dump_stack().
> dump_stack() will throw out the trace of the current
> task's stack at
> the point when it is called. See what happens when
> you place it in
> different places. Another option, if you ever have a
> hanging sytem is
> Alt-SysRq-T (presuming you have the magic option
> enabled and you are
> able to scrollback still), which pretty much calls
> dump_stack() for
> all available processes.
>
> -Nish
>
> --
> Kernelnewbies: Help each other learn about the Linux
> kernel.
> Archive:
> http://mail.nl.linux.org/kernelnewbies/
> FAQ: http://kernelnewbies.org/faq/
>
>
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
prev parent reply other threads:[~2004-11-23 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 15:31 how netfilter handles fragmented packets cranium2003
2004-11-21 16:15 ` Jan Engelhardt
2004-11-21 17:37 ` Nish Aravamudan
2004-11-21 19:42 ` cranium2003
2004-11-22 19:55 ` Nish Aravamudan
2004-11-23 6:07 ` cranium2003 [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=20041123060710.35447.qmail@web41406.mail.yahoo.com \
--to=cranium2003@yahoo.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=nish.aravamudan@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).