On Wed, 5 Apr 2023 at 11:00, syzbot <syzbot+list69b50efce6f847334104@xxxxxxxxxxxxxxxxxxxxxxxxx> 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
