From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+15c3ba3f7ca8ced0914d@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] INFO: rcu detected stall in fq_pie_timer (2)
Date: Fri, 29 Dec 2023 18:45:51 +0800 [thread overview]
Message-ID: <20231229104551.1876-1-hdanton@sina.com> (raw)
In-Reply-To: <000000000000a3123d060d7e22bd@google.com>
On Wed, 27 Dec 2023 05:54:18 -0800
> HEAD commit: 7c5e046bdcb2 Merge tag 'net-6.7-rc7' of git://git.kernel.o..
> git tree: net
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1127e71ae80000
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
--- x/net/sched/sch_fq_pie.c
+++ y/net/sched/sch_fq_pie.c
@@ -385,8 +385,7 @@ static void fq_pie_timer(struct timer_li
root_lock = qdisc_lock(qdisc_root_sleeping(sch));
spin_lock(root_lock);
- /* Limit this expensive loop to 2048 flows per round. */
- max_cnt = min_t(int, q->flows_cnt - q->flows_cursor, 2048);
+ max_cnt = min_t(int, q->flows_cnt - q->flows_cursor, 512);
for (i = 0; i < max_cnt; i++) {
pie_calculate_probability(&q->p_params,
&q->flows[q->flows_cursor].vars,
@@ -401,7 +400,7 @@ static void fq_pie_timer(struct timer_li
next = tupdate;
}
if (tupdate)
- mod_timer(&q->adapt_timer, jiffies + next);
+ mod_timer(&q->adapt_timer, jiffies + max(2, next));
spin_unlock(root_lock);
rcu_read_unlock();
}
--
next prev parent reply other threads:[~2023-12-29 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 13:54 syzbot
2023-12-28 12:06 ` Hillf Danton
2023-12-28 12:35 ` syzbot
2023-12-29 10:45 ` Hillf Danton [this message]
2023-12-29 11:10 ` syzbot
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=20231229104551.1876-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+15c3ba3f7ca8ced0914d@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®