From: syzbot <syzbot+listb2770ca7b7b9b9998f43@syzkaller.appspotmail.com>
To: jack@suse.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly udf report (Nov 2024)
Date: Mon, 18 Nov 2024 02:47:26 -0800 [thread overview]
Message-ID: <673b1b3e.050a0220.87769.0032.GAE@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, 1 new issues were detected and 0 were fixed.
In total, 7 issues are still open and 32 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 6085 Yes WARNING in udf_truncate_extents
https://syzkaller.appspot.com/bug?extid=43fc5ba6dcb33e3261ca
<2> 3712 Yes WARNING in drop_nlink (2)
https://syzkaller.appspot.com/bug?extid=651ca866e5e2b4b5095b
<3> 587 Yes WARNING in __udf_add_aext (3)
https://syzkaller.appspot.com/bug?extid=799a0e744ac47f928024
<4> 29 Yes WARNING in udf_setsize (2)
https://syzkaller.appspot.com/bug?extid=db6df8c0f578bc11e50e
<5> 17 Yes general protection fault in udf_read_folio
https://syzkaller.appspot.com/bug?extid=ddf8715339c89280b6fc
<6> 10 Yes KASAN: use-after-free Read in udf_update_tag
https://syzkaller.appspot.com/bug?extid=8743fca924afed42f93e
<7> 3 No possible deadlock in udf_free_blocks
https://syzkaller.appspot.com/bug?extid=d472c32c5dd4cd2fb5c5
---
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-11-18 10:47 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=673b1b3e.050a0220.87769.0032.GAE@google.com \
--to=syzbot+listb2770ca7b7b9b9998f43@syzkaller.appspotmail.com \
--cc=jack@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.