mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Hillf Danton <hdanton@sina.com>,
	syzbot <syzbot+27df43cf7ae73de7d8ee@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: BUG: soft lockup in ieee80211_tasklet_handler
Date: Tue, 02 Mar 2021 15:18:16 +0100	[thread overview]
Message-ID: <0a0573f07a7e1468f83d52afcf8f5ba356725740.camel@sipsolutions.net> (raw)
In-Reply-To: <20210224023026.3001-1-hdanton@sina.com>

On Wed, 2021-02-24 at 10:30 +0800, Hillf Danton wrote:
> 
> Add budget for the 80211 softint handler - it's feasible not to try to
> build the giant pyramid in a week.
> 
> --- x/net/mac80211/main.c
> +++ y/net/mac80211/main.c
> @@ -224,9 +224,15 @@ static void ieee80211_tasklet_handler(un
>  {
>  	struct ieee80211_local *local = (struct ieee80211_local *) data;
>  	struct sk_buff *skb;
> +	int i = 0;
> +
> +	while (i++ < 64) {
> +		skb = skb_dequeue(&local->skb_queue);
> +		if (!skb)
> +			skb = skb_dequeue(&local->skb_queue_unreliable);
> +		if (!skb)
> +			return;

I guess that's not such a bad idea, but I do wonder how we get here,
userspace can submit packets faster than we can process?

It feels like a simulation-only case, tbh, since over the air you have
limits how much bandwidth you can get ... unless you have a very slow
CPU?

In any case, if you want anything merged you're going to have to submit
a proper patch with a real commit message and Signed-off-by, etc.

johannes


  parent reply	other threads:[~2021-03-02 16:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 17:55 syzbot
2021-03-02  8:10 ` syzbot
     [not found] ` <20210224023026.3001-1-hdanton@sina.com>
2021-03-02 14:18   ` Johannes Berg [this message]
2021-03-02 19:01     ` Dmitry Vyukov
2021-03-04  8:30       ` Johannes Berg
     [not found]     ` <20210303085912.1647-1-hdanton@sina.com>
2021-03-03  9:06       ` Dmitry Vyukov

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=0a0573f07a7e1468f83d52afcf8f5ba356725740.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+27df43cf7ae73de7d8ee@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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

all inboxes | Powered by JetHome®