From: Hugh Dickins <hugh@veritas.com>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
linux-wireless@vger.kernel.org, ath5k-devel@venema.h4ckr.net
Subject: Re: [ath5k-devel] ath5k_tasklet_rx BUG_ON(bf->skb == NULL)
Date: Thu, 8 Jan 2009 16:18:56 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0901081603410.8411@blonde.anvils> (raw)
In-Reply-To: <1231426017.922.2.camel@maxim-laptop>
On Thu, 8 Jan 2009, Maxim Levitsky wrote:
> On Thu, 2009-01-08 at 13:49 +0000, Hugh Dickins wrote:
> >
> > When running swapping load tests, wireless alive but not in active use,
> > I've now twice hit the BUG_ON(bf->skb == NULL) in ath5k_tasklet_rx().
> >
> > So, that BUG_ON(bf->skb == NULL) appears to be unsafe under
> > memory pressure; but the fix wasn't obvious to me, so over
> > to you!
> >
> > I'd be glad to try patches, of course, but it's not happening
> > often enough for me to report back success quickly - unless I
> > stumble on a quicker way to reproduce it, it'll need a week or
> > two to grow confident of a fix.
>
> I use aspire one, and I don't see that, did this happen several times?
A couple of times, when running memory swapping loads: I doubt it
would be any problem when there's easily freeable memory around.
>
> Could you try compat-wireless:
>
> http://wireless.kernel.org/en/users/Download
Thanks, I've downloaded the tarball, but the difference between the
drivers/net/wireless/ath5k/base.c in there and in Linus's git is
very little: I'd be be very surprised if it fixes this bug.
As I said, it'll take a week or two to be confident that the issue
has been fixed, so I'd rather embark on that once a likely fix has
gone in.
(Of course, just removing the BUG_ON, and making sure there's
no oops on the NULL pointer, would fix my immediate issue:
but I doubt the right fix will be as simple as that.)
>
> It has many fixes that made my wireless on that notebook more or less
> usable.
I find 2.6.28's wireless very usable on that machine: I bet you're
a wireless specialist who stresses the wireless side of things in
ways I wouldn't begin to imagine: whereas I just browse and download
and scp a little, but as a memory specialist try swapping loads
which perhaps that driver had not been subjected to before.
Hugh
next prev parent reply other threads:[~2009-01-08 16:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 13:49 ath5k_tasklet_rx BUG_ON(bf->skb == NULL) Hugh Dickins
2009-01-08 14:46 ` [ath5k-devel] " Maxim Levitsky
2009-01-08 16:18 ` Hugh Dickins [this message]
2009-01-08 17:10 ` Bob Copeland
2009-01-08 17:55 ` Hugh Dickins
2009-01-08 18:41 ` Bob Copeland
2009-01-09 13:41 ` Bob Copeland
2009-01-09 14:10 ` Hugh Dickins
2009-01-10 16:47 ` Bob Copeland
2009-01-10 20:15 ` Bob Copeland
2009-01-13 15:35 ` Hugh Dickins
2009-01-13 15:56 ` Bob Copeland
2009-01-13 16:40 ` Hugh Dickins
2009-01-13 17:45 ` Luis R. Rodriguez
2009-02-06 13:12 ` Hugh Dickins
2009-02-06 18:37 ` Bob Copeland
2009-02-06 18:44 ` John W. Linville
2009-02-06 19:01 ` Hugh Dickins
2009-02-06 20:58 ` Bob Copeland
2009-02-09 2:30 ` Bob Copeland
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=Pine.LNX.4.64.0901081603410.8411@blonde.anvils \
--to=hugh@veritas.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@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