From: syzbot <syzbot+list0d9154e4f559c9f5f96f@syzkaller.appspotmail.com>
To: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [ext4] Monthly Report
Date: Fri, 24 Mar 2023 08:59:47 -0700 [thread overview]
Message-ID: <000000000000860b5105f7a77b97@google.com> (raw)
Hello ext4 maintainers/developers,
This is a 30-day syzbot report for ext4 subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/ext4
During the period, 17 new issues were detected and 4 were fixed.
In total, 94 issues are still open and 92 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
81778 Yes possible deadlock in jbd2_journal_lock_updates
https://syzkaller.appspot.com/bug?extid=79e6bbabf3ce17357969
34932 Yes possible deadlock in __jbd2_log_wait_for_space
https://syzkaller.appspot.com/bug?extid=fa1bbda326271b8808c9
6768 Yes WARNING in ext4_dirty_folio
https://syzkaller.appspot.com/bug?extid=ecab51a4a5b9f26eeaa1
4301 Yes possible deadlock in dquot_commit (2)
https://syzkaller.appspot.com/bug?extid=70ff52e51b7e7714db8a
846 Yes INFO: task hung in iterate_supers
https://syzkaller.appspot.com/bug?extid=2349f5067b1772c1d8a5
817 Yes BUG: soft lockup in smp_call_function
https://syzkaller.appspot.com/bug?extid=cce3691658bef1b12ac9
550 Yes INFO: task hung in __sync_dirty_buffer
https://syzkaller.appspot.com/bug?extid=91dccab7c64e2850a4e5
388 No possible deadlock in ext4_map_blocks
https://syzkaller.appspot.com/bug?extid=6de5025c31d33047d2a4
168 Yes possible deadlock in process_measurement (3)
https://syzkaller.appspot.com/bug?extid=ccfcdc8958f74084f16d
167 No INFO: task hung in path_openat (7)
https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
---
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-03-24 15:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000860b5105f7a77b97@google.com \
--to=syzbot+list0d9154e4f559c9f5f96f@syzkaller.appspotmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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