From: Grant Grundler <grundler@parisc-linux.org>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] kernel BUG at include/linux/skbuff.h:834!
Date: Fri, 8 Aug 2003 09:55:50 -0600 [thread overview]
Message-ID: <20030808155550.GE28214@dsl2.external.hp.com> (raw)
In-Reply-To: <20030806145700.GU22222@parcelfarce.linux.theplanet.co.uk>
On Wed, Aug 06, 2003 at 03:57:00PM +0100, Matthew Wilcox wrote:
> "I don't believe you" ;-)
Well, I just copied what the kernel posted to the console.
Maybe the stack trace was from the wrong stack? (kernel vs user space)
> The first BUG is in skb_put() and the second BUG is in skb_pull(). Neither
> are called from netif_receive_skb(), nor net_rx_action().
yup - I see that now too.
The stack info is crap unless the calls to skb_* are hidden
in macros or other inline function calls.
...
> So none of these addresses make any sense ;-(
ok. :^(
Hopefully this is reproducible.
grant
prev parent reply other threads:[~2003-08-08 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 14:32 [parisc-linux] kernel BUG at include/linux/skbuff.h:834! Grant Grundler
2003-08-06 14:57 ` Matthew Wilcox
2003-08-08 15:55 ` Grant Grundler [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=20030808155550.GE28214@dsl2.external.hp.com \
--to=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.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.