From: syzbot <syzbot+d9b3e95a78490389cfb7@syzkaller.appspotmail.com>
To: davem@davemloft.net, dcaratti@redhat.com, dsahern@kernel.org,
edumazet@google.com, jhs@mojatatu.com, jiri@resnulli.us,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, pctammela@mojatatu.com, shuah@kernel.org,
syzkaller-bugs@googlegroups.com, vinicius.gomes@intel.com,
vladimir.oltean@nxp.com, xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [net?] INFO: rcu detected stall in ipv6_rcv (4)
Date: Sat, 27 Jul 2024 02:16:02 -0700 [thread overview]
Message-ID: <000000000000b66dc7061e371339@google.com> (raw)
In-Reply-To: <0000000000004fe821060e0a68d1@google.com>
syzbot suspects this issue was fixed by commit:
commit fb66df20a7201e60f2b13d7f95d031b31a8831d3
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date: Mon May 27 15:39:55 2024 +0000
net/sched: taprio: extend minimum interval restriction to entire cycle too
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=179b2623980000
start commit: 2cf4f94d8e86 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=314e9ad033a7d3a7
dashboard link: https://syzkaller.appspot.com/bug?extid=d9b3e95a78490389cfb7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1487fc06e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11e5b4d6e80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net/sched: taprio: extend minimum interval restriction to entire cycle too
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-07-27 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 13:15 [syzbot] [net?] INFO: rcu detected stall in ipv6_rcv (4) syzbot
2024-07-27 9:16 ` syzbot [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=000000000000b66dc7061e371339@google.com \
--to=syzbot+d9b3e95a78490389cfb7@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=shuah@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vinicius.gomes@intel.com \
--cc=vladimir.oltean@nxp.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 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.