From: Jiri Kosina <jikos@kernel.org>
To: Peter Hutterer <peter.hutterer@who-t.net>
Cc: Andrey Konovalov <andreyknvl@google.com>,
syzbot <syzbot+6921abfb75d6fc79c0eb@syzkaller.appspotmail.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
amir73il@gmail.com, Felipe Balbi <balbi@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jan Kara <jack@suse.cz>,
kuba@kernel.org, linux-fsdevel@vger.kernel.org,
mathew.j.martineau@linux.intel.com, matthieu.baerts@tessares.net,
mptcp@lists.01.org, netdev <netdev@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: INFO: task hung in corrupted (2)
Date: Thu, 11 Jun 2020 08:58:06 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.2006110856290.13242@cbobk.fhfr.pm> (raw)
In-Reply-To: <20200611045118.GA306934@jelly>
On Thu, 11 Jun 2020, Peter Hutterer wrote:
> based on the line numbers it's the while loop in there which is also the one
> that could be unbounded if the hid collection isn't set up correctly or if
> we have some other corruption happening.
Given the fact this is syzkaller-induced, it's almost certainly a
completely bogus collection. So we are surely missing sanity check that
there exists a collection with idx -1.
> Need to page this back in to figure out what could be happening here.
Thanks,
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2020-06-11 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 11:30 INFO: task hung in corrupted (2) syzbot
2020-06-02 14:14 ` Andrey Konovalov
2020-06-04 11:41 ` Jiri Kosina
2020-06-11 4:51 ` Peter Hutterer
2020-06-11 6:58 ` Jiri Kosina [this message]
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=nycvar.YFH.7.76.2006110856290.13242@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=amir73il@gmail.com \
--cc=andreyknvl@google.com \
--cc=balbi@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.01.org \
--cc=netdev@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=syzbot+6921abfb75d6fc79c0eb@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).