On Sat, 04 Nov 2017 03:34:09 +0100, Jerome Glisse wrote: > > On Wed, Nov 01, 2017 at 01:02:27PM -0700, Andrew Morton wrote: > > Begin forwarded message: > > > > Date: Wed, 01 Nov 2017 12:54:16 -0700 > > From: syzbot <bot+63583aefef5457348dcfa06b87d4fd1378b26b09@xxxxxxxxxxxxxxxxxxxxxxxxx> > > To: aaron.lu@xxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, aneesh.kumar@xxxxxxxxxxxxxxxxxx, jack@xxxxxxx, kirill.shutemov@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, mhocko@xxxxxxxx, minchan@xxxxxxxxxx, peterz@xxxxxxxxxxxxx, rientjes@xxxxxxxxxx, sfr@xxxxxxxxxxxxxxxx, shli@xxxxxx, syzkaller-bugs@xxxxxxxxxxxxxxxx, willy@xxxxxxxxxxxxxxx, ying.huang@xxxxxxxxx, zi.yan@xxxxxxxxxxxxxx > > Subject: BUG: soft lockup > > > > > > Hello, > > > > syzkaller hit the following crash on > > 1d53d908b79d7870d89063062584eead4cf83448 > > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > > compiler: gcc (GCC) 7.1.1 20170620 > > .config is attached > > Raw console output is attached. > > C reproducer is attached > > syzkaller reproducer is attached. See https://goo.gl/kgGztJ > > for information about syzkaller reproducers > > Sorry to be the bringer of bad news but after: > 4842e98f26dd80be3623c4714a244ba52ea096a8 > and > 7e1d90f60a0d501c8503e636942ca704a454d910 > > The attached syzkaller repro trigger a softlockup in workqueue. I am unfamiliar > with that code so some familiar in that domain is more likely to find a proper > solution. > > Note with > git revert 7e1d90f60a0d501c8503e636942ca704a454d910 > git revert 4842e98f26dd80be3623c4714a244ba52ea096a8 > fix the issue Could you give the stack trace? thanks, Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
