From: Takashi Iwai Subject: Re: [PATCH 0/2] PCM OSS fixes Date: Mon, 08 Jan 2018 16:05:58 +0100 Message-ID: References: <20180108142541.18098-1-tiwai@suse.de> <87b0dddb-c9f4-5dc6-d6c4-1136c091c9fa@metafoo.de> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 0C7DD2673AF for ; Mon, 8 Jan 2018 16:05:58 +0100 (CET) In-Reply-To: <87b0dddb-c9f4-5dc6-d6c4-1136c091c9fa@metafoo.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Lars-Peter Clausen Cc: alsa-devel@alsa-project.org, Dmitry Vyukov List-Id: alsa-devel@alsa-project.org On Mon, 08 Jan 2018 15:58:47 +0100, Lars-Peter Clausen wrote: > > On 01/08/2018 03:25 PM, Takashi Iwai wrote: > > Hi, > > > > this contains two fixes for PCM OSS bugs that have been triggered by > > syzbot. These are simple and straightforward, and I'm going to queue > > for 4.15-rc8. > > I tried to reproduce the issue as well with the reproducer generated by > syzbot. But what syzbot reported was that the CPU didn't sleep for 140 > seconds. But with a long write() we'll go to sleep in between frames. So > when I tried the lockup detector never triggered. > > Were you able to reproduce the same CPU lockup as syzbot? Yes, I could reproduce RCU stalls with two reproducers (001a113ece5c2b600d05620b097a@google.com and 001a1147e1988b160a05620552eb@google.com) The patches seem curing them, so far, in combination with other patches in for-linus branch of sound.git tree. thanks, Takashi