[syzbot] Monthly integrity report (Dec 2024)

[syzbot]

Hello integrity maintainers/developers,

This is a 31-day syzbot report for the integrity subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/integrity

During the period, 0 new issues were detected and 0 were fixed.
In total, 3 issues are still open and 8 have already been fixed.

Some of the still happening issues:

Ref Crashes Repro Title
<1> 433 No INFO: task hung in process_measurement (2)
https://syzkaller.appspot.com/bug?extid=1de5a37cb85a2d536330
<2> 32 Yes KMSAN: uninit-value in ima_add_template_entry (2)
https://syzkaller.appspot.com/bug?extid=91ae49e1c1a2634d20c0
<3> 2 Yes INFO: task hung in ima_file_free (4)
https://syzkaller.appspot.com/bug?extid=8036326eebe7d0140944

---
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 syzk...@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.

[Roberto Sassu]

On Sat, 2024-12-07 at 08:13 -0800, syzbot wrote:
> Hello integrity maintainers/developers,
>
> This is a 31-day syzbot report for the integrity subsystem.
> All related reports/information can be found at:
> https://syzkaller.appspot.com/upstream/s/integrity
>
> During the period, 0 new issues were detected and 0 were fixed.
> In total, 3 issues are still open and 8 have already been fixed.
>
> Some of the still happening issues:
>
> Ref Crashes Repro Title
> <1> 433 No INFO: task hung in process_measurement (2)
> https://syzkaller.appspot.com/bug?extid=1de5a37cb85a2d536330
> <2> 32 Yes KMSAN: uninit-value in ima_add_template_entry (2)
> https://syzkaller.appspot.com/bug?extid=91ae49e1c1a2634d20c0

Hi Yuezhang

it seems that the patch causing the report above is:

6630ea49103c exfat: move extend valid_size into ->page_mkwrite()

Currently, didn't develop a fix for it. Could you please have a look?

Thanks

Roberto