From: syzbot <syzbot+c1cc0083f159b67cb192@syzkaller.appspotmail.com>
To: Jason@zx2c4.com, daniel.wippermann@resol.de, davem@davemloft.net,
edumazet@google.com, hdanton@sina.com, jason@zx2c4.com,
jhs@mojatatu.com, jiri@nvidia.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, pctammela@mojatatu.com,
syzkaller-bugs@googlegroups.com, victor@mojatatu.com,
vladimir.oltean@nxp.com, wireguard@lists.zx2c4.com
Subject: Re: [syzbot] [wireguard?] INFO: rcu detected stall in wg_ratelimiter_gc_entries (2)
Date: Fri, 29 Sep 2023 12:45:19 -0700 [thread overview]
Message-ID: <0000000000001be691060684aa2c@google.com> (raw)
In-Reply-To: <00000000000021dc2806031ad901@google.com>
syzbot suspects this issue was fixed by commit:
commit da71714e359b64bd7aab3bd56ec53f307f058133
Author: Jamal Hadi Salim <jhs@mojatatu.com>
Date: Tue Aug 22 10:12:31 2023 +0000
net/sched: fix a qdisc modification with ambiguous command request
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=129c464e680000
start commit: 8a519a572598 net: veth: Page pool creation error handling ..
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=3e670757e16affb
dashboard link: https://syzkaller.appspot.com/bug?extid=c1cc0083f159b67cb192
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=129f8553a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1205baada80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net/sched: fix a qdisc modification with ambiguous command request
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-09-29 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 9:15 [syzbot] [wireguard?] INFO: rcu detected stall in wg_ratelimiter_gc_entries (2) syzbot
2023-09-29 19:45 ` syzbot [this message]
[not found] <20230817102842.1706-1-hdanton@sina.com>
2023-08-17 11:37 ` syzbot
[not found] <20230818112605.2075-1-hdanton@sina.com>
2023-08-18 13:59 ` 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=0000000000001be691060684aa2c@google.com \
--to=syzbot+c1cc0083f159b67cb192@syzkaller.appspotmail.com \
--cc=Jason@zx2c4.com \
--cc=daniel.wippermann@resol.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=jhs@mojatatu.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=victor@mojatatu.com \
--cc=vladimir.oltean@nxp.com \
--cc=wireguard@lists.zx2c4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.