linux-kernel - Re: [syzbot] Monthly fuse report

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJfpegsGjFQX9t_NS8-oiE0K8Y0xEmr60VXMg6d4HQCCXOrOXg@mail.gmail.com>
Date:   Wed, 12 Apr 2023 15:52:37 +0200
From:   Miklos Szeredi <miklos@...redi.hu>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com,
        syzbot <syzbot+list69b50efce6f847334104@...kaller.appspotmail.com>
Subject: Re: [syzbot] Monthly fuse report

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