From: Daniel Vetter <daniel@ffwll.ch>
To: syzbot <syzbot+1e46a0864c1a6e9bd3d8@syzkaller.appspotmail.com>
Cc: airlied@linux.ie, intel-gfx@lists.freedesktop.org,
syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, dri-devel@lists.freedesktop.org,
shli@kernel.org
Subject: Re: WARNING in md_ioctl
Date: Tue, 26 Nov 2019 09:42:53 +0100 [thread overview]
Message-ID: <20191126084253.GP29965@phenom.ffwll.local> (raw)
In-Reply-To: <000000000000f4160705983366e8@google.com>
On Mon, Nov 25, 2019 at 02:37:01PM -0800, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 4b6ce6810a5dc0af387a238e8c852e0d3822381f
> Author: Rafael Antognolli <rafael.antognolli@intel.com>
> Date: Mon Feb 5 23:33:30 2018 +0000
>
> drm/i915/cnl: WaPipeControlBefore3DStateSamplePattern
This seems very unlikely, the reproducer doesn't open a drm device, and
I'd be surprised if your gcd instances have an actual i915 device in them
(but I can't check because boot log isn't provided, didn't find it on the
dashboard either).
Since i915 is built-in I suspect this simply moved something else in the
kernel image around which provokes the bug.
-Daniel
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13aeb522e00000
> start commit: c61a56ab Merge branch 'x86-urgent-for-linus' of git://git...
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=106eb522e00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=17aeb522e00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=4013180e7c7a9ff9
> dashboard link: https://syzkaller.appspot.com/bug?extid=1e46a0864c1a6e9bd3d8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16bca207800000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14819a47800000
>
> Reported-by: syzbot+1e46a0864c1a6e9bd3d8@syzkaller.appspotmail.com
> Fixes: 4b6ce6810a5d ("drm/i915/cnl:
> WaPipeControlBefore3DStateSamplePattern")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-26 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 1:00 WARNING in md_ioctl syzbot
2019-11-25 22:37 ` syzbot
2019-11-26 8:42 ` Daniel Vetter [this message]
2020-10-17 11:06 Dae R. Jeong
2020-10-19 6:18 ` Song Liu
2020-10-19 7:03 ` Dae R. Jeong
2020-10-21 5:28 ` Song Liu
2020-10-22 0:24 ` Dae R. Jeong
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=20191126084253.GP29965@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
--cc=syzbot+1e46a0864c1a6e9bd3d8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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).