From: syzbot <syzbot+list26a7aeaa369adf7a9a57@syzkaller.appspotmail.com>
To: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly cgroups report (Aug 2025)
Date: Fri, 29 Aug 2025 05:52:31 -0700 [thread overview]
Message-ID: <68b1a28f.a00a0220.1337b0.0018.GAE@google.com> (raw)
Hello cgroups maintainers/developers,
This is a 31-day syzbot report for the cgroups subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/cgroups
During the period, 2 new issues were detected and 1 were fixed.
In total, 9 issues are still open and 39 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3949 Yes possible deadlock in task_rq_lock
https://syzkaller.appspot.com/bug?extid=ca14b36a46a8c541b509
<2> 246 Yes possible deadlock in console_flush_all (4)
https://syzkaller.appspot.com/bug?extid=d10e9d53059eb8aed654
<3> 105 No WARNING in css_rstat_flush
https://syzkaller.appspot.com/bug?extid=7a605e85e5b5a7e4a5e3
<4> 69 No BUG: unable to handle kernel paging request in percpu_ref_get_many (2)
https://syzkaller.appspot.com/bug?extid=3109abc43c8fcf15212b
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2025-08-29 12:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=68b1a28f.a00a0220.1337b0.0018.GAE@google.com \
--to=syzbot+list26a7aeaa369adf7a9a57@syzkaller.appspotmail.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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.