From: syzbot <syzbot+listfc277c7cb94932601d96@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly lsm report (Sep 2024)
Date: Mon, 23 Sep 2024 02:02:22 -0700 [thread overview]
Message-ID: <66f12e9e.050a0220.3eed3.0009.GAE@google.com> (raw)
Hello lsm maintainers/developers,
This is a 31-day syzbot report for the lsm subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/lsm
During the period, 0 new issues were detected and 0 were fixed.
In total, 4 issues are still open and 27 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 306 No INFO: task hung in process_measurement (2)
https://syzkaller.appspot.com/bug?extid=1de5a37cb85a2d536330
<2> 9 No general protection fault in smack_inode_permission
https://syzkaller.appspot.com/bug?extid=4ac565a7081cc43bb185
<3> 3 Yes WARNING in current_check_refer_path
https://syzkaller.appspot.com/bug?extid=34b68f850391452207df
---
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.
next reply other threads:[~2024-09-23 9:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 9:02 syzbot [this message]
2024-09-23 12:06 ` [syzbot] Monthly lsm report (Sep 2024) Paul Moore
2024-09-23 16:15 ` Casey Schaufler
2024-09-28 0:18 ` Casey Schaufler
2024-09-24 11:53 ` Roberto Sassu
2024-09-27 12:18 ` Roberto Sassu
2024-09-28 0:08 ` Kent Overstreet
2024-09-28 1:25 ` Kent Overstreet
2024-09-28 6:49 ` Tetsuo Handa
2024-09-28 8:57 ` Kent Overstreet
2024-09-28 9:23 ` Tetsuo Handa
2024-09-28 17:40 ` Kent Overstreet
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=66f12e9e.050a0220.3eed3.0009.GAE@google.com \
--to=syzbot+listfc277c7cb94932601d96@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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