From: syzbot <syzbot+a9317fe7ad261fc76b88@syzkaller.appspotmail.com>
To: andy@greyhouse.net, davem@davemloft.net,
dri-devel@lists.freedesktop.org, gregkh@linuxfoundation.org,
j.vosburgh@gmail.com, linaro-mm-sig-owner@lists.linaro.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, maheshb@google.com,
netdev@vger.kernel.org, sumit.semwal@linaro.org,
syzkaller-bugs@googlegroups.com, vfalico@gmail.com
Subject: Re: WARNING in dma_buf_vunmap
Date: Wed, 20 Mar 2019 18:21:00 -0700 [thread overview]
Message-ID: <0000000000000d28ac0584908d43@google.com> (raw)
In-Reply-To: <000000000000aa8703057a7ea0bb@google.com>
syzbot has bisected this bug to:
commit d5e73f7be850323ae3adbbe84ed37a38b0c31476
Author: Mahesh Bandewar <maheshb@google.com>
Date: Wed Mar 8 18:55:51 2017 +0000
bonding: restructure arp-monitor
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15e679f7200000
start commit: d5e73f7b bonding: restructure arp-monitor
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=17e679f7200000
console output: https://syzkaller.appspot.com/x/log.txt?x=13e679f7200000
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
Reported-by: syzbot+a9317fe7ad261fc76b88@syzkaller.appspotmail.com
Fixes: d5e73f7b ("bonding: restructure arp-monitor")
next prev parent reply other threads:[~2019-03-21 1:21 UTC|newest]
Thread overview: 7+ 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 [this message]
2019-11-07 13:42 ` syzbot
2019-11-07 13:42 ` syzbot
2019-11-11 13:54 ` Hans Verkuil
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=0000000000000d28ac0584908d43@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=j.vosburgh@gmail.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=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=syzkaller-bugs@googlegroups.com \
--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 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.