On Sun, 08 Apr 2018 15:26:21 +0200, Tetsuo Handa wrote: > > Dmitry Vyukov wrote: > > Takashi has already fixed this. See this thread: > > https://groups.google.com/forum/#!searchin/syzkaller-bugs/%22INFO$3A$20rcu$20detected$20stall$20in$20snd_pcm_oss_write3$20(2)%22%7Csort:date/syzkaller-bugs/D2xWV7WTRDk/sCw_gImmCAAJ > > Yes, I noticed it just before I post this. But the reason I posted this anyway > is that I feel that there is some other bug revealed by this reproducer. > How can Takashi' patch explain my observation (with linux-next-20180406) ? The bug is triggered by any buffer underrun of a PCM stream via OSS emulation, so the condition can vary in any form. That is, if an app doesn't give the enough amount in time, the PCM goes to XRUN state. Then at closing, the driver tries to sync the pending data and hits the bug. Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
