From: syzbot <syzbot+52d2f6feb48dc7328968@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, davem@davemloft.net,
hdanton@sina.com, hpa@zytor.com, jhs@mojatatu.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, pctammela@mojatatu.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
victor@mojatatu.com, vladimir.oltean@nxp.com, x86@kernel.org
Subject: Re: [syzbot] [kernel?] INFO: rcu detected stall in toggle_allocation_gate
Date: Wed, 27 Sep 2023 07:12:22 -0700 [thread overview]
Message-ID: <000000000000adbe11060657c7b6@google.com> (raw)
In-Reply-To: <00000000000029708206031ad94a@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=15dd4876680000
start commit: 950fe35831af Merge branch 'ipv6-expired-routes'
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=fe63ad15dded26b6
dashboard link: https://syzkaller.appspot.com/bug?extid=52d2f6feb48dc7328968
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13d34703a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13a9a040680000
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-27 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 9:15 [syzbot] [kernel?] INFO: rcu detected stall in toggle_allocation_gate syzbot
2023-09-27 14:12 ` syzbot [this message]
[not found] <20230817104037.1766-1-hdanton@sina.com>
2023-08-17 12:01 ` 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=000000000000adbe11060657c7b6@google.com \
--to=syzbot+52d2f6feb48dc7328968@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=hdanton@sina.com \
--cc=hpa@zytor.com \
--cc=jhs@mojatatu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pctammela@mojatatu.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=victor@mojatatu.com \
--cc=vladimir.oltean@nxp.com \
--cc=x86@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 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.