Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <000000000000d5a93805f8930638@google.com>
In-Reply-To: <000000000000d5a93805f8930638@google.com>
From:   Miklos Szeredi <miklos@szeredi.hu>
Date:   Wed, 12 Apr 2023 15:52:37 +0200
Message-ID: <CAJfpegsGjFQX9t_NS8-oiE0K8Y0xEmr60VXMg6d4HQCCXOrOXg@mail.gmail.com>
Subject: Re: [syzbot] Monthly fuse report
To:     Dmitry Vyukov <dvyukov@google.com>
Cc:     linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
        syzkaller-bugs@googlegroups.com,
        syzbot <syzbot+list69b50efce6f847334104@syzkaller.appspotmail.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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