From: syzbot <syzbot+fc9127d4bfa8ef129f7d@syzkaller.appspotmail.com>
To: bp@alien8.de, brauner@kernel.org, dave.hansen@linux.intel.com,
edumazet@google.com, hdanton@sina.com, hpa@zytor.com,
jhs@mojatatu.com, linux-kernel@vger.kernel.org,
michal.kubiak@intel.com, mingo@redhat.com, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: [syzbot] [kernel?] INFO: rcu detected stall in drain_vmap_area_work
Date: Thu, 28 Sep 2023 19:46:15 -0700 [thread overview]
Message-ID: <000000000000a0708b0606766d7b@google.com> (raw)
In-Reply-To: <0000000000006452210601115981@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=111ab276680000
start commit: fdf0eaf11452 Linux 6.5-rc2
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=77b9a3cf8f44c6da
dashboard link: https://syzkaller.appspot.com/bug?extid=fc9127d4bfa8ef129f7d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103a7aaaa80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=177aa662a80000
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-29 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 11:04 [syzbot] [kernel?] INFO: rcu detected stall in drain_vmap_area_work syzbot
2023-09-29 2:46 ` syzbot [this message]
[not found] <20230722231824.905-1-hdanton@sina.com>
2023-07-22 23:38 ` 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=000000000000a0708b0606766d7b@google.com \
--to=syzbot+fc9127d4bfa8ef129f7d@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=hpa@zytor.com \
--cc=jhs@mojatatu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.kubiak@intel.com \
--cc=mingo@redhat.com \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox