From: syzbot <syzbot+listc3adb3676e5a9d135247@syzkaller.appspotmail.com>
To: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly arm report (Apr 2024)
Date: Tue, 30 Apr 2024 00:12:27 -0700 [thread overview]
Message-ID: <000000000000b25bef06174b1755@google.com> (raw)
Hello arm maintainers/developers,
This is a 31-day syzbot report for the arm subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/arm
During the period, 2 new issues were detected and 0 were fixed.
In total, 7 issues are still open and 4 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1634 Yes BUG: bad usercopy in fpa_set
https://syzkaller.appspot.com/bug?extid=cb76c2983557a07cdb14
<2> 350 Yes INFO: task hung in lookup_slow (3)
https://syzkaller.appspot.com/bug?extid=7cfc6a4f6b025f710423
<3> 37 No WARNING in delayed_work_timer_fn
https://syzkaller.appspot.com/bug?extid=e13e654d315d4da1277c
<4> 18 Yes BUG: unable to handle kernel paging request in trans_pgd_create_copy
https://syzkaller.appspot.com/bug?extid=2d1f5a94167d430a3bd7
<5> 9 No WARNING in do_sve_acc
https://syzkaller.appspot.com/bug?extid=95ffb6a83b20ea7f4f55
---
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-04-30 7:12 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=000000000000b25bef06174b1755@google.com \
--to=syzbot+listc3adb3676e5a9d135247@syzkaller.appspotmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).