From: syzbot <syzbot+liste6fcb39e599cf6bcae03@syzkaller.appspotmail.com>
To: jack@suse.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly udf report (Nov 2023)
Date: Thu, 09 Nov 2023 10:23:26 -0800 [thread overview]
Message-ID: <000000000000c0279e0609bc4c7a@google.com> (raw)
Hello udf maintainers/developers,
This is a 31-day syzbot report for the udf subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/udf
During the period, 0 new issues were detected and 0 were fixed.
In total, 14 issues are still open and 18 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1759 Yes WARNING in udf_truncate_extents
https://syzkaller.appspot.com/bug?extid=43fc5ba6dcb33e3261ca
<2> 103 Yes KASAN: use-after-free Write in udf_close_lvid
https://syzkaller.appspot.com/bug?extid=60864ed35b1073540d57
<3> 28 Yes WARNING in udf_new_block
https://syzkaller.appspot.com/bug?extid=cc717c6c5fee9ed6e41d
<4> 15 Yes WARNING in invalidate_bh_lru
https://syzkaller.appspot.com/bug?extid=9743a41f74f00e50fc77
<5> 13 Yes WARNING in udf_setsize (2)
https://syzkaller.appspot.com/bug?extid=db6df8c0f578bc11e50e
<6> 6 Yes UBSAN: array-index-out-of-bounds in udf_process_sequence
https://syzkaller.appspot.com/bug?extid=abb7222a58e4ebc930ad
<7> 5 Yes KASAN: slab-out-of-bounds Write in udf_adinicb_writepage
https://syzkaller.appspot.com/bug?extid=a3db10baf0c0ee459854
<8> 2 Yes KASAN: slab-use-after-free Read in udf_free_blocks
https://syzkaller.appspot.com/bug?extid=0b7937459742a0a4cffd
---
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:[~2023-11-09 18:23 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=000000000000c0279e0609bc4c7a@google.com \
--to=syzbot+liste6fcb39e599cf6bcae03@syzkaller.appspotmail.com \
--cc=jack@suse.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).