mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+list046505ae3554066e8ffe@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-dev-en@lists.osdn.me
Subject: [syzbot] Monthly tomoyo report (Dec 2024)
Date: Thu, 19 Dec 2024 10:40:21 -0800	[thread overview]
Message-ID: <67646895.050a0220.1dcc64.0023.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, 3 new issues were detected and 0 were fixed.
In total, 3 issues are still open and 11 have already been fixed.

Some of the still happening issues:

Ref Crashes Repro Title
<1> 22      Yes   general protection fault in tomoyo_gc_thread
                  https://syzkaller.appspot.com/bug?extid=bf6351831bc4f9148d98
<2> 6       No    BUG: corrupted list in tomoyo_try_to_gc
                  https://syzkaller.appspot.com/bug?extid=e92661ab419d1a81b816
<3> 5       No    general protection fault in tomoyo_check_acl (4)
                  https://syzkaller.appspot.com/bug?extid=2232f2316fe61cb50344

---
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:[~2024-12-19 18:40 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=67646895.050a0220.1dcc64.0023.GAE@google.com \
    --to=syzbot+list046505ae3554066e8ffe@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-dev-en@lists.osdn.me \
    /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

all inboxes | Powered by JetHome®