Re: INFO: rcu detected stall in io_playback_transfer

2018-04-09 Thread Takashi Iwai
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/D2xW

Re: INFO: rcu detected stall in io_playback_transfer

2018-04-08 Thread Tetsuo Handa
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.

Re: INFO: rcu detected stall in io_playback_transfer

2018-04-08 Thread Dmitry Vyukov
On Sun, Apr 8, 2018 at 2:58 PM, Tetsuo Handa wrote: > I manually simplified the reproducer. > > It is quite strange that removing unshare() hides this lockup bug. > Also, explicitly closing by "close()" hides this lockup bug. > Triggering "fput() from do_exit()" from "different namespace" > someho

Re: INFO: rcu detected stall in io_playback_transfer

2018-04-08 Thread Tetsuo Handa
I manually simplified the reproducer. It is quite strange that removing unshare() hides this lockup bug. Also, explicitly closing by "close()" hides this lockup bug. Triggering "fput() from do_exit()" from "different namespace" somehow affects this lockup bug?