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 c

Re: INFO: task hung in corrupted (2)

On Thu, Jun 04, 2020 at 01:41:07PM +0200, Jiri Kosina wrote: > On Tue, 2 Jun 2020, Andrey Konovalov wrote: > > > > Hello, > > > > > > syzbot found the following crash on: > > > > > > HEAD commit:b0c3ba31 Merge tag 'fsnotify_for_v5.7-rc8' of > > > git://git.ke.. > > > git tree: upstream

Re: INFO: task hung in corrupted (2)

On Tue, 2 Jun 2020, Andrey Konovalov wrote: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:b0c3ba31 Merge tag 'fsnotify_for_v5.7-rc8' of git://git.ke.. > > git tree: upstream > > console output: https://syzkaller.appspot.com/x/log.txt?x=14089eee10 > > ker

INFO: task hung in corrupted (2)

Hello, syzbot found the following crash on: HEAD commit:b0c3ba31 Merge tag 'fsnotify_for_v5.7-rc8' of git://git.ke.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14089eee10 kernel config: https://syzkaller.appspot.com/x/.config?x=ce116858301bc2ea das