From: syzbot <syzbot+0468b73bdbb243217224@syzkaller.appspotmail.com>
To: hverkuil-cisco@xs4all.nl, kyungmin.park@samsung.com,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
m.szyprowski@samsung.com, mchehab+samsung@kernel.org,
mchehab@kernel.org, pawel@osciak.com,
syzkaller-bugs@googlegroups.com, tfiga@chromium.org
Subject: Re: KASAN: null-ptr-deref Read in refcount_sub_and_test_checked (2)
Date: Fri, 06 Dec 2019 17:30:00 -0800 [thread overview]
Message-ID: <000000000000dc7fc70599131995@google.com> (raw)
In-Reply-To: <00000000000057e614057a9abcd3@google.com>
syzbot suspects this bug was fixed by commit:
commit 62dcb4f41836bd3c44b5b651bb6df07ea4cb1551
Author: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Date: Thu Nov 8 12:23:37 2018 +0000
media: vb2: check memory model for VIDIOC_CREATE_BUFS
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14972e41e00000
start commit: ccda4af0 Linux 4.20-rc2
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=4a0a89f12ca9b0f5
dashboard link: https://syzkaller.appspot.com/bug?extid=0468b73bdbb243217224
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16d20893400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=118f5a2b400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: media: vb2: check memory model for VIDIOC_CREATE_BUFS
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-12-07 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 7:18 KASAN: null-ptr-deref Read in refcount_sub_and_test_checked (2) syzbot
2019-03-21 17:39 ` syzbot
2019-12-07 1:30 ` 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=000000000000dc7fc70599131995@google.com \
--to=syzbot+0468b73bdbb243217224@syzkaller.appspotmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@kernel.org \
--cc=pawel@osciak.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tfiga@chromium.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.