From: syzbot <syzbot+43cc00d616820666f675@syzkaller.appspotmail.com>
To: edumazet@google.com, hdanton@sina.com, jhs@mojatatu.com,
linux-kernel@vger.kernel.org, michal.kubiak@intel.com,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] [kernel?] INFO: rcu detected stall in sys_clock_nanosleep (5)
Date: Thu, 28 Sep 2023 01:34:13 -0700 [thread overview]
Message-ID: <0000000000003341ba0606672c7a@google.com> (raw)
In-Reply-To: <0000000000003dcc9306031affdd@google.com>
syzbot suspects this issue was fixed by commit:
commit 8c21ab1bae945686c602c5bfa4e3f3352c2452c5
Author: Eric Dumazet <edumazet@google.com>
Date: Tue Aug 29 12:35:41 2023 +0000
net/sched: fq_pie: avoid stalls in fq_pie_timer()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12958976680000
start commit: 6709d4b7bc2e net: nfc: Fix use-after-free caused by nfc_ll..
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=2cbd298d0aff1140
dashboard link: https://syzkaller.appspot.com/bug?extid=43cc00d616820666f675
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10858fc0a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14781270a80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net/sched: fq_pie: avoid stalls in fq_pie_timer()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-09-28 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 9:25 [syzbot] [kernel?] INFO: rcu detected stall in sys_clock_nanosleep (5) syzbot
2023-09-28 8:34 ` syzbot [this message]
[not found] <20230817104922.1822-1-hdanton@sina.com>
2023-08-17 12:23 ` 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=0000000000003341ba0606672c7a@google.com \
--to=syzbot+43cc00d616820666f675@syzkaller.appspotmail.com \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=jhs@mojatatu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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.