From: syzbot <syzbot+list7dc14b213a3187ae72f0@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
penguin-kernel@I-love.SAKURA.ne.jp,
syzkaller-bugs@googlegroups.com, takedakn@nttdata.co.jp,
tomoyo-users_en@lists.sourceforge.net
Subject: [syzbot] Monthly tomoyo report (Jun 2026)
Date: Sat, 20 Jun 2026 05:32:38 -0700 [thread overview]
Message-ID: <6a368866.5c48295d.477b4.001a.GAE@google.com> (raw)
Hello tomoyo maintainers/developers,
This is a 31-day syzbot report for the tomoyo subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/tomoyo
During the period, 1 new issues were detected and 0 were fixed.
In total, 3 issues are still open and 12 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 558 Yes INFO: rcu detected stall in sys_newfstatat (4)
https://syzkaller.appspot.com/bug?extid=1c02a56102605204445c
<2> 1 No KMSAN: uninit-value in tomoyo_path_chown (3)
https://syzkaller.appspot.com/bug?extid=eaae8fa60ce81f1e4eeb
<3> 100 Yes INFO: rcu detected stall in sys_symlinkat (5)
https://syzkaller.appspot.com/bug?extid=9618c3b34a3062164a21
---
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:[~2026-06-20 12:32 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=6a368866.5c48295d.477b4.001a.GAE@google.com \
--to=syzbot+list7dc14b213a3187ae72f0@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=syzkaller-bugs@googlegroups.com \
--cc=takedakn@nttdata.co.jp \
--cc=tomoyo-users_en@lists.sourceforge.net \
/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