From: syzbot <syzbot+05835159fe322770fe3d@syzkaller.appspotmail.com>
To: a@unstable.cc, airlied@linux.ie, airlied@redhat.com,
alexander.deucher@amd.com, b.a.t.m.a.n@lists.open-mesh.org,
christian.koenig@amd.com, daniel@ffwll.ch, davem@davemloft.net,
dri-devel@lists.freedesktop.org, gregkh@linuxfoundation.org,
hdegoede@redhat.com, kraxel@redhat.com,
linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com,
mareklindner@neomailbox.ch, mripard@kernel.org,
netdev@vger.kernel.org, noralf@tronnes.org,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, tzimmermann@suse.de
Subject: Re: WARNING in idr_destroy
Date: Tue, 10 Mar 2020 21:36:02 -0700 [thread overview]
Message-ID: <00000000000019196205a08cc67d@google.com> (raw)
In-Reply-To: <0000000000002e20b9059fee8a94@google.com>
syzbot has bisected this bug to:
commit 5b3709793d151e6e12eb6a38a5da3f7fc2923d3a
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date: Wed May 8 08:26:19 2019 +0000
drm/ast: Convert AST driver to |struct drm_gem_vram_object|
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15a66fb5e00000
start commit: 63623fd4 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=17a66fb5e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=13a66fb5e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d2e033af114153f
dashboard link: https://syzkaller.appspot.com/bug?extid=05835159fe322770fe3d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e978e3e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10b1a819e00000
Reported-by: syzbot+05835159fe322770fe3d@syzkaller.appspotmail.com
Fixes: 5b3709793d15 ("drm/ast: Convert AST driver to |struct drm_gem_vram_object|")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2020-03-11 4:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0000000000002e20b9059fee8a94@google.com>]
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=00000000000019196205a08cc67d@google.com \
--to=syzbot+05835159fe322770fe3d@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mareklindner@neomailbox.ch \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tzimmermann@suse.de \
/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).