From: syzbot <syzbot+48b0652a95834717f190@syzkaller.appspotmail.com>
To: albinbabuvarghese20@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fbdev?] KASAN: vmalloc-out-of-bounds Write in imageblit (5)
Date: Thu, 02 Oct 2025 00:43:02 -0700 [thread overview]
Message-ID: <68de2d06.a00a0220.102ee.007d.GAE@google.com> (raw)
In-Reply-To: <CADfthj02rbyq6dhxB_DT=znADAUjLhKmWY8FLDq7z9k05-UdbQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+48b0652a95834717f190@syzkaller.appspotmail.com
Tested-by: syzbot+48b0652a95834717f190@syzkaller.appspotmail.com
Tested on:
commit: 7f707257 Merge tag 'kbuild-6.18-1' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=128e1334580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c0e9f5ceb8894f4a
dashboard link: https://syzkaller.appspot.com/bug?extid=48b0652a95834717f190
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=13ac45cd980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-10-02 7:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADfthj02rbyq6dhxB_DT=znADAUjLhKmWY8FLDq7z9k05-UdbQ@mail.gmail.com>
2025-10-02 7:43 ` syzbot [this message]
[not found] <CADfthj1NsOSdy-Mry0CNr+kx1Rw6gdFy9hN45n-WqLbpbxVZaA@mail.gmail.com>
2025-10-05 9:14 ` [syzbot] [fbdev?] KASAN: vmalloc-out-of-bounds Write in imageblit (5) syzbot
[not found] <CADfthj35b15UzKe5wz4QDPUfEobf1ddU3T6XDyDHGSJySBg5jw@mail.gmail.com>
2025-09-27 3:59 ` syzbot
[not found] <CADfthj0xkbKwihXm-_gkCr0Arw3OU9fF=d1GdLNspniTDwLwTA@mail.gmail.com>
2025-09-25 14:29 ` syzbot
[not found] <CADfthj1pNb0LhZy9dTMAavNXNdJxMnNdWj2LQiaAf-iO4Dn7Mw@mail.gmail.com>
2025-09-25 14:05 ` syzbot
2025-09-08 19:19 syzbot
2025-09-15 15:59 ` syzbot
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=68de2d06.a00a0220.102ee.007d.GAE@google.com \
--to=syzbot+48b0652a95834717f190@syzkaller.appspotmail.com \
--cc=albinbabuvarghese20@gmail.com \
--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 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.