From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, tom@dbservice.com
Subject: Re: [Bugme-new] [Bug 33842] New: NULL pointer dereference in ip_fragment
Date: Mon, 25 Apr 2011 21:29:40 -0700 [thread overview]
Message-ID: <20110425212940.a2e9dad7.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-33842-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sat, 23 Apr 2011 07:51:56 GMT bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=33842
>
> Summary: NULL pointer dereference in ip_fragment
oops in ip_defragment(). Kernel is 2.6.39-rc4. There are some
screenshots attached to the report.
> Product: Networking
> Version: 2.5
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: acme@ghostprotocols.net
> ReportedBy: tom@dbservice.com
> Regression: No
>
>
> The host is using the ath9k driver. eth0+wlan0 are bridged. Shortly after I
> start using the wireless network with my macbook, the bug triggers. No idea if
> it's wireless related, because there's also a rtl8169_rx_interrupt entry in the
> stacktrace.
>
> This is a transcript, since I don't (have/know of) any way to get the backtrace
> out of a crashed box.
>
> IP: ip_fragment+0x52/0x840
> Call Trace:
> <IRQ>
> br_parse_ip_options
> br_flood_deliver
> br_parse_ip_options
> br_nf_dev_queue_xmit
> br_nf_post_routing
> nf_iterate
>
> then also:
> lots of br_flood_deliver
> lots of br_*_finish
> one ? rtl8169_interrupt
> one ? ath9k_ioread32
>
next parent reply other threads:[~2011-04-26 4:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-33842-10286@https.bugzilla.kernel.org/>
2011-04-26 4:29 ` Andrew Morton [this message]
2011-04-26 20:31 [Bugme-new] [Bug 33842] New: NULL pointer dereference in ip_fragment Bandan Das
2011-04-26 20:46 ` David Miller
2011-04-26 20:53 ` Eric Dumazet
2011-04-26 20:59 ` Bandan Das
2011-04-26 21:01 ` Eric Dumazet
2011-04-26 21:19 ` Bandan Das
2011-04-26 21:24 ` Eric Dumazet
2011-04-27 7:22 ` Tomas Carnecky
2011-04-27 7:41 ` Eric Dumazet
2011-04-27 11:52 ` Tomas Carnecky
2011-04-27 12:17 ` Eric Dumazet
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=20110425212940.a2e9dad7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tom@dbservice.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 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.