[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <nycvar.YFH.7.76.2006110856290.13242@cbobk.fhfr.pm>
Date: Thu, 11 Jun 2020 08:58:06 +0200 (CEST)
From: Jiri Kosina <jikos@...nel.org>
To: Peter Hutterer <peter.hutterer@...-t.net>
cc: Andrey Konovalov <andreyknvl@...gle.com>,
syzbot <syzbot+6921abfb75d6fc79c0eb@...kaller.appspotmail.com>,
Benjamin Tissoires <benjamin.tissoires@...hat.com>,
"open list:HID CORE LAYER" <linux-input@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
amir73il@...il.com, Felipe Balbi <balbi@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jan Kara <jack@...e.cz>, kuba@...nel.org,
linux-fsdevel@...r.kernel.org, mathew.j.martineau@...ux.intel.com,
matthieu.baerts@...sares.net, mptcp@...ts.01.org,
netdev <netdev@...r.kernel.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: INFO: task hung in corrupted (2)
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
Powered by blists - more mailing lists