From: Johannes Berg <johannes@sipsolutions.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: b43 crash with fragmented packet
Date: Tue, 23 Aug 2011 23:08:15 -0700 [thread overview]
Message-ID: <1314166095.4719.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1314163238.4478.8.camel@edumazet-laptop> (sfid-20110824_074509_254388_9F8F7B58)
On Wed, 2011-08-24 at 07:20 +0200, Eric Dumazet wrote:
> Le mardi 23 août 2011 à 19:28 -0700, Johannes Berg a écrit :
> > Just had a crash in mac80211 with an apparently fragmented packet
> > (segfault in ieee80211_rx_h_defragment), I can send the stacktrace but I
> > can't make much sense of it -- anyone see something similar?
> >
>
>
>
> Send it, preferably to netdev, since its probably more suited ;)
Err, I guess I messed up, I meant to send this to linux-wireless, sorry
folks.
johannes
prev parent reply other threads:[~2011-08-24 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 2:28 b43 crash with fragmented packet Johannes Berg
2011-08-24 5:20 ` Eric Dumazet
2011-08-24 6:08 ` Johannes Berg [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=1314166095.4719.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox