From: syzbot <syzbot+9fe09db3795456e0b442@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, rohithmatham@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [usb?] WARNING in corrupted (4)
Date: Thu, 29 Oct 2026 00:33:01 -0700 [thread overview]
Message-ID: <6ae2f6ad.5451848c.f7707.0007.GAE@google.com> (raw)
In-Reply-To: <CA+FtcEpVevUcS4pbiCebTJ4noA2H=3K3VZq+-jJ=4=BJNsmEXw@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+9fe09db3795456e0b442@syzkaller.appspotmail.com
Tested-by: syzbot+9fe09db3795456e0b442@syzkaller.appspotmail.com
Tested on:
commit: 5b0764a5 Merge tag 'drm-next-2026-10-21' of https://gi..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=10ab8b31580000
kernel config: https://syzkaller.appspot.com/x/.config?x=fd1433abd362f255
dashboard link: https://syzkaller.appspot.com/bug?extid=9fe09db3795456e0b442
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
userspace arch: i386
patch: https://syzkaller.appspot.com/x/patch.diff?x=149d49e1580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-10-29 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+FtcEpVevUcS4pbiCebTJ4noA2H=3K3VZq+-jJ=4=BJNsmEXw@mail.gmail.com>
2026-10-29 7:33 ` syzbot [this message]
[not found] <179311142878.187144.14168935384418059345@kernel.org>
2026-10-27 16:41 ` [syzbot] [mm?] [usb?] WARNING in corrupted (4) syzbot
2026-10-27 12:08 syzbot
2026-10-27 17:10 ` Andrew Morton
2026-11-11 5:49 ` Rohith Matam
2026-11-11 5:56 ` Rohith Matam
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=6ae2f6ad.5451848c.f7707.0007.GAE@google.com \
--to=syzbot+9fe09db3795456e0b442@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rohithmatham@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.