From: syzbot <syzbot+272ce7abd8e49c0ddf42@syzkaller.appspotmail.com>
To: hverkuil-cisco@xs4all.nl, hverkuil@xs4all.nl,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
liushixin2@huawei.com, mchehab@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: vmalloc-out-of-bounds Write in tpg_fill_plane_buffer (2)
Date: Fri, 27 Jan 2023 13:45:23 -0800 [thread overview]
Message-ID: <00000000000058e86005f345c88f@google.com> (raw)
In-Reply-To: <00000000000065419205cb454ac4@google.com>
syzbot suspects this issue was fixed by commit:
commit 94a7ad9283464b75b12516c5512541d467cefcf8
Author: Liu Shixin <liushixin2@huawei.com>
Date: Thu Oct 27 12:38:55 2022 +0000
media: vivid: fix compose size exceed boundary
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10a3509e480000
start commit: f1583cb1be35 Merge tag 'linux-kselftest-next-5.15-rc1' of ..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=9c582b69de20dde2
dashboard link: https://syzkaller.appspot.com/bug?extid=272ce7abd8e49c0ddf42
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f79ecd300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1489a4c9300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: media: vivid: fix compose size exceed boundary
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-01-27 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 20:22 [syzbot] KASAN: vmalloc-out-of-bounds Write in tpg_fill_plane_buffer (2) syzbot
2023-01-27 21:45 ` syzbot [this message]
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=00000000000058e86005f345c88f@google.com \
--to=syzbot+272ce7abd8e49c0ddf42@syzkaller.appspotmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=mchehab@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.