[syzbot] Monthly fuse report

2 views
Skip to first unread message

syzbot

unread,
Apr 5, 2023, 5:00:43 AM4/5/23
to linux-...@vger.kernel.org, linux-...@vger.kernel.org, mik...@szeredi.hu, syzkall...@googlegroups.com
Hello fuse maintainers/developers,

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

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

Some of the still happening issues:

Crashes Repro Title
146 Yes INFO: task hung in fuse_simple_request
https://syzkaller.appspot.com/bug?extid=46fe899420456e014d6b
26 Yes INFO: task hung in lookup_slow (3)
https://syzkaller.appspot.com/bug?extid=7cfc6a4f6b025f710423
13 Yes INFO: task hung in walk_component (5)
https://syzkaller.appspot.com/bug?extid=8fba0e0286621ce71edd

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

Miklos Szeredi

unread,
Apr 12, 2023, 9:52:51 AM4/12/23
to Dmitry Vyukov, linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com, syzbot
On Wed, 5 Apr 2023 at 11:00, syzbot
<syzbot+list69b5...@syzkaller.appspotmail.com> wrote:
>
> Hello fuse maintainers/developers,
>
> This is a 30-day syzbot report for the fuse subsystem.
> All related reports/information can be found at:
> https://syzkaller.appspot.com/upstream/s/fuse
>
> During the period, 0 new issues were detected and 0 were fixed.
> In total, 8 issues are still open and 34 have been fixed so far.
>
> Some of the still happening issues:
>
> Crashes Repro Title
> 146 Yes INFO: task hung in fuse_simple_request
> https://syzkaller.appspot.com/bug?extid=46fe899420456e014d6b
> 26 Yes INFO: task hung in lookup_slow (3)
> https://syzkaller.appspot.com/bug?extid=7cfc6a4f6b025f710423
> 13 Yes INFO: task hung in walk_component (5)
> https://syzkaller.appspot.com/bug?extid=8fba0e0286621ce71edd

Hi Dmitry,

These all look like non-kernel deadlocks.

AFAIR syzbot was taught about breaking these by "umount -f" or "echo 1
> /sys/fs/fuse/connections/$DEV/abort", right?

I wonder why they are still triggering a report then.

Thanks,
Miklos

Aleksandr Nogikh

unread,
Apr 14, 2023, 11:09:56 AM4/14/23
to Miklos Szeredi, Dmitry Vyukov, linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com, syzbot
Hi Miklos,

syzbot indeed writes 0x1 to each /sys/fs/fuse/connections/%s/abort
See https://github.com/google/syzkaller/blob/ec410564b9e4ff241d1242febb29eda2ee28b50d/executor/common_linux.h#L4614

Some C reproducers (e.g.
https://syzkaller.appspot.com/text?tag=ReproC&x=128284a0b00000) also
contain that piece of code.

--
Aleksandr

>
> I wonder why they are still triggering a report then.
>
> Thanks,
> Miklos
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/CAJfpegsGjFQX9t_NS8-oiE0K8Y0xEmr60VXMg6d4HQCCXOrOXg%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages