From: syzbot <syzbot+59a71007ccac79e8bb69@syzkaller.appspotmail.com>
To: david@redhat.com, hverkuil-cisco@xs4all.nl, hverkuil@xs4all.nl,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
m.szyprowski@samsung.com, mchehab@kernel.org,
syzkaller-bugs@googlegroups.com, tfiga@chromium.org,
torvalds@linux-foundation.org
Subject: Re: [syzbot] [media?] WARNING in get_vaddr_frames
Date: Thu, 26 Oct 2023 04:53:07 -0700 [thread overview]
Message-ID: <0000000000001ff5ed06089d37f1@google.com> (raw)
In-Reply-To: <0000000000003a5c4905ef1044d6@google.com>
syzbot suspects this issue was fixed by commit:
commit 735de5caf79e06cc9fb96b1b4f4974674ae3e917
Author: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Date: Thu Aug 17 10:41:32 2023 +0000
media: vb2: frame_vector.c: replace WARN_ONCE with a comment
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16c7ad5d680000
start commit: 53663f4103ff Merge tag 'nfs-for-6.5-2' of git://git.linux-..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1b32f62c755c3a9c
dashboard link: https://syzkaller.appspot.com/bug?extid=59a71007ccac79e8bb69
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=178be4b7a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=107609a7a80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: media: vb2: frame_vector.c: replace WARN_ONCE with a comment
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-10-26 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 8:13 [syzbot] WARNING in get_vaddr_frames syzbot
2023-01-21 8:03 ` syzbot
2023-01-21 19:44 ` Linus Torvalds
2023-10-26 11:53 ` 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=0000000000001ff5ed06089d37f1@google.com \
--to=syzbot+59a71007ccac79e8bb69@syzkaller.appspotmail.com \
--cc=david@redhat.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tfiga@chromium.org \
--cc=torvalds@linux-foundation.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