From: syzbot <syzbot+59a71007ccac79e8bb69@syzkaller.appspotmail.com>
To: 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] WARNING in get_vaddr_frames
Date: Sat, 21 Jan 2023 00:03:30 -0800 [thread overview]
Message-ID: <000000000000107e1b05f2c19aa5@google.com> (raw)
In-Reply-To: <0000000000003a5c4905ef1044d6@google.com>
syzbot has bisected this issue to:
commit 6647e76ab623b2b3fb2efe03a86e9c9046c52c33
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu Dec 1 00:10:52 2022 +0000
v4l2: don't fall back to follow_pfn() if pin_user_pages_fast() fails
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=115987c5480000
start commit: e4cf7c25bae5 Merge tag 'kbuild-fixes-v6.2' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=135987c5480000
console output: https://syzkaller.appspot.com/x/log.txt?x=155987c5480000
kernel config: https://syzkaller.appspot.com/x/.config?x=2651619a26b4d687
dashboard link: https://syzkaller.appspot.com/bug?extid=59a71007ccac79e8bb69
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16ee1934480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=101b997c480000
Reported-by: syzbot+59a71007ccac79e8bb69@syzkaller.appspotmail.com
Fixes: 6647e76ab623 ("v4l2: don't fall back to follow_pfn() if pin_user_pages_fast() fails")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-21 8:03 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 [this message]
2023-01-21 19:44 ` Linus Torvalds
2023-10-26 11:53 ` [syzbot] [media?] " 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=000000000000107e1b05f2c19aa5@google.com \
--to=syzbot+59a71007ccac79e8bb69@syzkaller.appspotmail.com \
--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 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.