Re: INFO: task hung in chaoskey_disconnect

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quoting Oliver Neukum (2019-11-20 02:55:49)
> Am Freitag, den 15.11.2019, 09:51 -0800 schrieb Stephen Boyd:
> > Quoting syzbot (2019-11-06 04:32:09)
> > > Hello,
> > > 
> > > syzbot found the following crash on:
> > > 
> > > HEAD commit:    b1aa9d83 usb: raw: add raw-gadget interface
> > > git tree:       https://github.com/google/kasan.git usb-fuzzer
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=16ae2adce00000
> > > kernel config:  https://syzkaller.appspot.com/x/.config?x=79de80330003b5f7
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=f41c4f7c6d8b0b778780
> > > compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> > > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10248158e00000
> > > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16afbf7ce00000
> > > 
> > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > Reported-by: syzbot+f41c4f7c6d8b0b778780@xxxxxxxxxxxxxxxxxxxxxxxxx
> > 
> > I suspect this is because of the kthread getting stuck problem reported
> > by Maciej. Maybe try the commit that Herbert picked up.
> 
> Do you have a commit ID so we can test an exported patch?
> 

I sent the patch in. See https://lkml.kernel.org/r/00000000000019acd8059770942b@xxxxxxxxxx
for what happened. It didn't make a difference. I'll have to stare at it
a little more to figure out what's going on.





[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux