linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artur Skawina <art.08.09@gmail.com>
To: Christian Lamparter <chunkeey@web.de>
Cc: Artur Skawina <art.08.09@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [RFC][RFT][PATCH] p54usb: rx refill revamp
Date: Thu, 22 Jan 2009 22:45:44 +0100	[thread overview]
Message-ID: <4978E908.4060103@gmail.com> (raw)
In-Reply-To: <200901222239.29656.chunkeey@web.de>

Christian Lamparter wrote:
> On Thursday 22 January 2009 16:43:20 Artur Skawina wrote:
>> Christian Lamparter wrote:
>>> On Thursday 22 January 2009 00:22:16 Artur Skawina wrote:
>>> +	if (unlikely(!priv->common.hw->workqueue)) {
>>> +		/*
>>> +		 * Huh? mac80211 isn't fully initialized yet?
>>> +		 * Please check your system, something bad is going on.
>>> +		 */
>>> +		WARN_ON(1);
>> please do not add WARN_ON's unless you're actually interested in the
>> stacktrace, In this case it's a usb completion, so in most cases the
>> backtrace isn't very interesting, wouldn't a printk be enough?
>> [i was hitting this when testing, and it took several seconds to 
>> get all the data to the console]
> 
> Ahh, wait!
> 
> In fact we "should" call BUG_ON here, as mac80211 is not fully initialized at
> this point and we might have accidently submitted a dataframe to the stack.
> (Of course, this attempt by the device to send garbage to the stack is
> caught by the common-code... so no oops here)

Wouldn't you then want to catch it _before_ p54_rx()?

> However, I wonder if the WARN_ON gets triggered under normal operation or not.
> (Just in case, no it does not trigger with the ISL3887 chips)

i have never seen it, after the initial 32 times.
As-is, it currently triggers on every init however...

artur

  reply	other threads:[~2009-01-22 21:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 13:50 [RFC][RFT][PATCH] p54usb: rx refill revamp Christian Lamparter
2009-01-21 16:04 ` Artur Skawina
2009-01-21 18:24   ` Christian Lamparter
2009-01-21 19:32     ` Artur Skawina
2009-01-21 20:56       ` Christian Lamparter
2009-01-21 23:22         ` Artur Skawina
2009-01-22 15:00           ` Christian Lamparter
2009-01-22 15:43             ` Artur Skawina
2009-01-22 21:39               ` Christian Lamparter
2009-01-22 21:45                 ` Artur Skawina [this message]
2009-01-22 22:12                   ` Christian Lamparter
2009-01-22  5:40       ` Artur Skawina
2009-01-22 15:09         ` Christian Lamparter
2009-01-22 15:52           ` Artur Skawina
2009-01-22 16:01             ` Christian Lamparter
2009-01-22 19:19               ` Artur Skawina
2009-01-22 21:02                 ` Christian Lamparter
2009-01-22 22:05                   ` Artur Skawina
2009-01-22 22:39                     ` Christian Lamparter
2009-01-22 22:51                       ` Artur Skawina
2009-01-23  1:11                     ` Artur Skawina
2009-01-21 20:06 ` Larry Finger
2009-01-21 20:51   ` Christian Lamparter

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=4978E908.4060103@gmail.com \
    --to=art.08.09@gmail.com \
    --cc=chunkeey@web.de \
    --cc=linux-wireless@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).