From: Eric Dumazet <eric.dumazet@gmail.com>
To: syzbot <syzbot+c22c6b9dce8e773ddcb6@syzkaller.appspotmail.com>,
davem@davemloft.net, edumazet@google.com, jhs@mojatatu.com,
jiri@resnulli.us, kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
xiyou.wangcong@gmail.com
Subject: Re: INFO: rcu detected stall in addrconf_rs_timer (3)
Date: Sun, 26 Jan 2020 11:12:11 -0800 [thread overview]
Message-ID: <7f746a56-07d9-282d-02b6-1724350b90b7@gmail.com> (raw)
In-Reply-To: <0000000000003021ea059d0c98b4@google.com>
On 1/26/20 7:25 AM, syzbot wrote:
> syzbot suspects this bug was fixed by commit:
>
> commit d9e15a2733067c9328fb56d98fe8e574fa19ec31
> Author: Eric Dumazet <edumazet@google.com>
> Date: Mon Jan 6 14:10:39 2020 +0000
>
> pkt_sched: fq: do not accept silly TCA_FQ_QUANTUM
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1625d479e00000
> start commit: a1ec57c0 net: stmmac: tc: Fix TAPRIO division operation
> git tree: net-next
> kernel config: https://syzkaller.appspot.com/x/.config?x=7159d94cd4de714e
> dashboard link: https://syzkaller.appspot.com/bug?extid=c22c6b9dce8e773ddcb6
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=168e33b6e00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=178c160ae00000
>
> If the result looks correct, please mark the bug fixed by replying with:
>
> #syz fix: pkt_sched: fq: do not accept silly TCA_FQ_QUANTUM
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
This sounds legit.
#syz fix: pkt_sched: fq: do not accept silly TCA_FQ_QUANTUM
prev parent reply other threads:[~2020-01-26 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 2:35 INFO: rcu detected stall in addrconf_rs_timer (3) syzbot
2020-01-26 15:25 ` syzbot
2020-01-26 19:12 ` Eric Dumazet [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=7f746a56-07d9-282d-02b6-1724350b90b7@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+c22c6b9dce8e773ddcb6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).