linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Hugh Dickins <hugh@veritas.com>,
	ath5k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org,
	Jiri Slaby <jirislaby@gmail.com>,
	maximlevitsky@gmail.com
Subject: Re: [ath5k-devel] ath5k_tasklet_rx BUG_ON(bf->skb == NULL)
Date: Fri, 6 Feb 2009 13:44:46 -0500	[thread overview]
Message-ID: <20090206184445.GB7526@tuxdriver.com> (raw)
In-Reply-To: <20090206183443.M95991@bobcopeland.com>

On Fri, Feb 06, 2009 at 01:37:49PM -0500, Bob Copeland wrote:
> On Fri, 6 Feb 2009 13:12:34 +0000 (GMT), Hugh Dickins wrote
> > Hi Bob,
> > 
> > On Tue, 13 Jan 2009, Bob Copeland wrote:
> > > On Tue, 13 Jan 2009 15:35:29 +0000 (GMT), Hugh Dickins wrote
> > > > But I haven't seen any allocation failure for several days.
> > > > I didn't get any while trying to simplify the reproduction,
> > > 
> > > I'll go ahead and push this upstream then today or tomorrow; let me 
> > > know if you run into any problems with more testing.
> > 
> > Just a prod: I've not seen your fix go into the 2.6.29-rc tree yet.
> 
> Good point, it is queued for 2.6.30.  John, would there be any problem
> with including a8e3cd514, "ath5k: fix bf->skb==NULL panic in 
> ath5k_tasklet_rx" for 2.6.29?

Hmmm...well it is a little big, but I guess it is OK.  Do you have
an example of the stack trace?  Or a link to a bugzilla or somesuch
would be even better...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-02-06 18:45 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
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 [this message]
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=20090206184445.GB7526@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=hugh@veritas.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --cc=me@bobcopeland.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;
as well as URLs for NNTP newsgroup(s).