linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: mac80211 splat with pktgen on hacked 4.4 kernel.
Date: Wed, 15 Jun 2016 10:46:20 -0700	[thread overview]
Message-ID: <5761946C.80101@candelatech.com> (raw)
In-Reply-To: <576192B2.3000304@candelatech.com>

On 06/15/2016 10:38 AM, Ben Greear wrote:
> On 4.4.11 + local hacks, including fairly extensive pktgen changes....
>
> When I overdrive transmit on a station with pktgen, I see this
> splat hit below repeatedly.  Any ideas on what kinds of things
> might cause this?
>
>          while (!skb_queue_empty(&local->pending[i])) {
>              struct sk_buff *skb = __skb_dequeue(&local->pending[i]);
>              struct ieee80211_tx_info *info = IEEE80211_SKB_CB(skb);
>
>              if (WARN_ON(!info->control.vif)) {
>                  ieee80211_free_txskb(&local->hw, skb);
>                  continue;
>              }
>

For instance, should this method below set the vif when it is queueing up a backlogged
frame when the queue is stopped?  Seems it only sets the vif it it is transmitting
the frame?

static bool ieee80211_tx_frags(struct ieee80211_local *local,
                                struct ieee80211_vif *vif,
                                struct ieee80211_sta *sta,
                                struct sk_buff_head *skbs,
                                bool txpending)

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2016-06-15 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 17:38 mac80211 splat with pktgen on hacked 4.4 kernel Ben Greear
2016-06-15 17:46 ` Ben Greear [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=5761946C.80101@candelatech.com \
    --to=greearb@candelatech.com \
    --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).