From: syzbot <syzbot+a9317fe7ad261fc76b88@syzkaller.appspotmail.com>
To: andy@greyhouse.net, davem@davemloft.net,
dri-devel@lists.freedesktop.org, gregkh@linuxfoundation.org,
hverkuil-cisco@xs4all.nl, j.vosburgh@gmail.com,
kyungmin.park@samsung.com, linaro-mm-sig-owner@lists.linaro.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, m.szyprowski@samsung.com,
maheshb@google.com, mchehab+samsung@kernel.org,
mchehab@kernel.org, netdev@vger.kernel.org, pawel@osciak.com,
sumit.semwal@linaro.org, syzkaller-bugs@googlegroups.com,
tfiga@chromium.org, vfalico@gmail.com
Subject: Re: WARNING in dma_buf_vunmap
Date: Thu, 07 Nov 2019 05:42:06 -0800 [thread overview]
Message-ID: <000000000000d2c94e0596c1d47b@google.com> (raw)
In-Reply-To: <000000000000aa8703057a7ea0bb@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=116af11c600000
start commit: d41217aa Merge tag 'pci-v4.20-fixes-1' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=4a0a89f12ca9b0f5
dashboard link: https://syzkaller.appspot.com/bug?extid=a9317fe7ad261fc76b88
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16f7b6f5400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=105a2783400000
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
next prev parent reply other threads:[~2019-11-07 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 21:46 WARNING in dma_buf_vunmap syzbot
2018-11-15 7:39 ` syzbot
2019-03-21 1:21 ` syzbot
2019-11-07 13:42 ` syzbot [this message]
2019-11-11 13:54 ` Hans Verkuil
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=000000000000d2c94e0596c1d47b@google.com \
--to=syzbot+a9317fe7ad261fc76b88@syzkaller.appspotmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=j.vosburgh@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linaro-mm-sig-owner@lists.linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=maheshb@google.com \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pawel@osciak.com \
--cc=sumit.semwal@linaro.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tfiga@chromium.org \
--cc=vfalico@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).