mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+listb80138072a82b574f50f@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	song@kernel.org,  syzkaller-bugs@googlegroups.com,
	yukuai@fygo.io
Subject: [syzbot] Monthly raid report (Nov 2026)
Date: Tue, 03 Nov 2026 04:33:30 -0800	[thread overview]
Message-ID: <6ae9d49a.26d36f6c.15fe18.0009.GAE@google.com> (raw)

Hello raid maintainers/developers,

This is a 31-day syzbot report for the raid subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/raid

During the period, 0 new issues were detected and 1 were fixed.
In total, 3 issues are still open and 11 have already been fixed.
There are also 4 low-priority issues.

Some of the still happening issues:

Ref Crashes Repro Title
<1> 43      Yes   BUG: unable to handle kernel paging request in free_conf
                  https://syzkaller.appspot.com/bug?extid=270624bb31d478afe62e
<2> 29      Yes   general protection fault in md_handle_request
                  https://syzkaller.appspot.com/bug?extid=89a9ab2a134d092fffae
<3> 21      Yes   UBSAN: array-index-out-of-bounds in super_90_sync
                  https://syzkaller.appspot.com/bug?extid=9e3014263a35700ab49b

---
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-11-03 12: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=6ae9d49a.26d36f6c.15fe18.0009.GAE@google.com \
    --to=syzbot+listb80138072a82b574f50f@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yukuai@fygo.io \
    /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®