linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+list69b50efce6f847334104@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	miklos@szeredi.hu, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly fuse report
Date: Wed, 05 Apr 2023 02:00:42 -0700	[thread overview]
Message-ID: <000000000000d5a93805f8930638@google.com> (raw)

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 syzkaller@googlegroups.com.

             reply	other threads:[~2023-04-05  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05  9:00 syzbot [this message]
2023-04-12 13:52 ` [syzbot] Monthly fuse report Miklos Szeredi
2023-04-14 15:09   ` Aleksandr Nogikh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=000000000000d5a93805f8930638@google.com \
    --to=syzbot+list69b50efce6f847334104@syzkaller.appspotmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).