From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: netdev <netdev@vger.kernel.org>, Jiri Benc <jbenc@suse.cz>
Subject: Re: d80211 oops with bcm43xx-d80211
Date: Fri, 15 Dec 2006 16:26:16 +0100 [thread overview]
Message-ID: <1166196376.3462.26.camel@johannes.berg> (raw)
In-Reply-To: <200612151623.07036.mb@bu3sch.de>
[-- Attachment #1: Type: text/plain, Size: 517 bytes --]
On Fri, 2006-12-15 at 16:23 +0100, Michael Buesch wrote:
> It turns out to oops only sometimes for me.
> And if, then with some very strange looking oopses.
Yeah but that's probably because most of the stacktrace is from whatever
was running when the softirq was run...
> > the instruction c003030c is in the middle of tasklet_action and it's a
> > free-after-use type of thing as you can see from accessing 0x6b6b6b73,
>
> use-after-free?
yes, but the "use" is "trying to run tasklet"
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2006-12-15 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 14:56 d80211 oops with bcm43xx-d80211 Johannes Berg
2006-12-15 15:23 ` Michael Buesch
2006-12-15 15:26 ` 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=1166196376.3462.26.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=jbenc@suse.cz \
--cc=mb@bu3sch.de \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).