From: syzbot <syzbot+list7fec1c4497e9462aa056@syzkaller.appspotmail.com>
To: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly cgroups report (Feb 2025)
Date: Sun, 23 Feb 2025 14:20:28 -0800 [thread overview]
Message-ID: <67bb9f2c.050a0220.bbfd1.003d.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, 1 new issues were detected and 0 were fixed.
In total, 7 issues are still open and 38 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4312 Yes possible deadlock in console_flush_all (3)
https://syzkaller.appspot.com/bug?extid=18cfb7f63482af8641df
<2> 3250 Yes possible deadlock in task_rq_lock
https://syzkaller.appspot.com/bug?extid=ca14b36a46a8c541b509
<3> 98 Yes possible deadlock in console_lock_spinning_enable (5)
https://syzkaller.appspot.com/bug?extid=622acb507894a48b2ce9
<4> 5 Yes general protection fault in __cgroup_rstat_lock
https://syzkaller.appspot.com/bug?extid=31eb4d4e7d9bc1fc1312
<5> 3 No BUG: unable to handle kernel paging request in memcg_rstat_updated
https://syzkaller.appspot.com/bug?extid=c62387c3885ca12e1255
---
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-02-23 22:20 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=67bb9f2c.050a0220.bbfd1.003d.GAE@google.com \
--to=syzbot+list7fec1c4497e9462aa056@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox