Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John W Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Print unknown packet type in tasklet_handler
Date: Thu, 18 Dec 2008 16:23:55 +0100	[thread overview]
Message-ID: <1229613835.3601.3.camel@johannes.berg> (raw)
In-Reply-To: <49496093.ddL5Pgdq/zMZM8op%Larry.Finger@lwfinger.net>

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

On Wed, 2008-12-17 at 14:26 -0600, Larry Finger wrote:
> In stress testing p54usb, the WARN_ON() in ieee80211_tasklet_handler() was
> triggered; however, there is no logging of the received value for packet
> type. Adding that feature will improve the warning.
> 
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>

Acked-by: Johannes Berg <johannes@sipsolutions.net>

> ---
> 
> John.
> 
> This is 2.6.29 material.
> 
> Larry
> ---
> 
> Index: wireless-testing/net/mac80211/main.c
> ===================================================================
> --- wireless-testing.orig/net/mac80211/main.c
> +++ wireless-testing/net/mac80211/main.c
> @@ -341,7 +341,8 @@ static void ieee80211_tasklet_handler(un
>  			dev_kfree_skb(skb);
>  			break ;
>  		default:
> -			WARN_ON(1);
> +			WARN(1, "mac80211: Packet is of unknown type %d\n",
> +			     skb->pkt_type);
>  			dev_kfree_skb(skb);
>  			break;
>  		}
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2008-12-18 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 20:26 [PATCH] mac80211: Print unknown packet type in tasklet_handler Larry Finger
2008-12-18 15:23 ` 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=1229613835.3601.3.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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