From: syzbot <syzbot+afb3084a933aa2bdacc6@syzkaller.appspotmail.com>
To: a@unstable.cc, b.a.t.m.a.n@lists.open-mesh.org,
bpf@vger.kernel.org, davem@davemloft.net, dsahern@kernel.org,
edumazet@google.com, kuba@kernel.org, kuniyu@amazon.com,
linux-kernel@vger.kernel.org, mareklindner@neomailbox.ch,
netdev@vger.kernel.org, pabeni@redhat.com, sven@narfation.org,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
vinicius.gomes@intel.com
Subject: Re: [syzbot] [batman?] INFO: rcu detected stall in rtnl_newlink (3)
Date: Sat, 14 Oct 2023 06:07:28 -0700 [thread overview]
Message-ID: <000000000000ec9cb90607acdac9@google.com> (raw)
In-Reply-To: <000000000000ea44c905ffd26705@google.com>
syzbot suspects this issue was fixed by commit:
commit e739718444f7bf2fa3d70d101761ad83056ca628
Author: Kuniyuki Iwashima <kuniyu@amazon.com>
Date: Sat Jul 29 00:07:05 2023 +0000
net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15b26a4d680000
start commit: d528014517f2 Revert ".gitignore: ignore *.cover and *.mbx"
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d576750da57ebbb5
dashboard link: https://syzkaller.appspot.com/bug?extid=afb3084a933aa2bdacc6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15849d08a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13184990a80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2023-10-14 13:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000ea44c905ffd26705@google.com>]
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=000000000000ec9cb90607acdac9@google.com \
--to=syzbot+afb3084a933aa2bdacc6@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sven@narfation.org \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vinicius.gomes@intel.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).