From: Greg KH <gregkh@linuxfoundation.org>
To: syzbot <syzbot+111bc509cd9740d7e4aa@syzkaller.appspotmail.com>
Cc: bp@alien8.de, devel@driverdev.osuosl.org,
douly.fnst@cn.fujitsu.com, dvyukov@google.com,
forest@alittletooquiet.net, hpa@zytor.com,
konrad.wilk@oracle.com, len.brown@intel.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mingo@redhat.com, peterz@infradead.org, puwen@hygon.cn,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tvboxspy@gmail.com, wang.yi59@zte.com.cn, x86@kernel.org
Subject: Re: WARNING in rcu_check_gp_start_stall
Date: Sun, 17 Mar 2019 12:04:47 +0100 [thread overview]
Message-ID: <20190317110447.GA3885@kroah.com> (raw)
In-Reply-To: <0000000000009b8d8a058447efc5@google.com>
On Sun, Mar 17, 2019 at 03:43:01AM -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit f1e3e92135202ff3d95195393ee62808c109208c
> Author: Malcolm Priestley <tvboxspy@gmail.com>
> Date: Wed Jul 22 18:16:42 2015 +0000
>
> staging: vt6655: fix tagSRxDesc -> next_desc type
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=111856cf200000
> start commit: f1e3e921 staging: vt6655: fix tagSRxDesc -> next_desc type
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=131856cf200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=151856cf200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=7132344728e7ec3f
> dashboard link: https://syzkaller.appspot.com/bug?extid=111bc509cd9740d7e4aa
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16d4966cc00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10c492d0c00000
>
> Reported-by: syzbot+111bc509cd9740d7e4aa@syzkaller.appspotmail.com
> Fixes: f1e3e921 ("staging: vt6655: fix tagSRxDesc -> next_desc type")
I think syzbot is a bit confused here, how can this simple patch, where
you do not have the hardware for this driver, cause this problem?
thanks,
greg k-h
next prev parent reply other threads:[~2019-03-17 11:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 17:10 WARNING in rcu_check_gp_start_stall syzbot
2019-02-22 22:20 ` Borislav Petkov
2019-02-23 10:33 ` Dmitry Vyukov
2019-02-23 10:38 ` Borislav Petkov
2019-02-23 10:50 ` Dmitry Vyukov
2019-02-23 10:56 ` Borislav Petkov
2019-03-17 10:43 ` syzbot
2019-03-17 11:04 ` Greg KH [this message]
2019-03-18 12:18 ` Dmitry Vyukov
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=20190317110447.GA3885@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=devel@driverdev.osuosl.org \
--cc=douly.fnst@cn.fujitsu.com \
--cc=dvyukov@google.com \
--cc=forest@alittletooquiet.net \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=puwen@hygon.cn \
--cc=syzbot+111bc509cd9740d7e4aa@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tvboxspy@gmail.com \
--cc=wang.yi59@zte.com.cn \
--cc=x86@kernel.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 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).