From: syzbot <syzbot+list47ee4443aeac8f86ebca@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
syzkaller-bugs@googlegroups.com, ulf.hansson@linaro.org
Subject: [syzbot] Monthly mmc report (Oct 2026)
Date: Sat, 03 Oct 2026 21:33:40 -0700 [thread overview]
Message-ID: <6ac1d724.34119e79.2f92f3.001c.GAE@google.com> (raw)
Hello mmc maintainers/developers,
This is a 31-day syzbot report for the mmc subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/mmc
During the period, 2 new issues were detected and 0 were fixed.
In total, 13 issues are still open.
There is also 1 low-priority issue.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 865 No INFO: task hung in mmc_stop_host
https://syzkaller.appspot.com/bug?extid=d0688023306aea3aefdc
<2> 401 No INFO: task hung in sdio_reset
https://syzkaller.appspot.com/bug?extid=e8678cd3d8b65d1f2c74
<3> 354 No WARNING: suspicious RCU usage in cancel_delayed_work_sync
https://syzkaller.appspot.com/bug?extid=9c1988bc953fca2086a3
<4> 193 No INFO: task hung in mmc_go_idle
https://syzkaller.appspot.com/bug?extid=bb55e8118af00556efa2
<5> 128 No WARNING: suspicious RCU usage in mmc_free_host
https://syzkaller.appspot.com/bug?extid=0d22039ef0915696ad4b
<6> 80 No INFO: task hung in mmc_io_rw_direct_host
https://syzkaller.appspot.com/bug?extid=fd993974345f022e97f2
<7> 69 No INFO: task hung in mmc_send_if_cond_pcie
https://syzkaller.appspot.com/bug?extid=30341f17551668478919
<8> 65 Yes WARNING: ODEBUG bug in vub300_disconnect
https://syzkaller.appspot.com/bug?extid=f4a0159ce6802a0a4774
<9> 63 No INFO: task hung in mmc_send_io_op_cond
https://syzkaller.appspot.com/bug?extid=15adedb55f72fa957b00
<10> 41 No WARNING in mmc_free_host
https://syzkaller.appspot.com/bug?extid=82a0a7de6d84867d030e
---
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.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2026-10-04 4:33 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=6ac1d724.34119e79.2f92f3.001c.GAE@google.com \
--to=syzbot+list47ee4443aeac8f86ebca@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ulf.hansson@linaro.org \
/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
all inboxes | Powered by JetHome®