From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rene Herman Subject: [PATCH 3/4] alsa-kernel: schedule_timeout() fix for core/seq/seq_instr.c Date: Tue, 18 Sep 2007 16:27:36 +0200 Message-ID: <46EFE058.2030300@gmail.com> References: <46E58D01.9080809@gmail.com> <46EF18FF.7070906@gmail.com> <46EF3097.7060300@gmail.com> <46EF52E4.90401@gmail.com> <46EFD955.1000601@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from smtpq1.tilbu1.nb.home.nl (smtpq1.tilbu1.nb.home.nl [213.51.146.200]) by alsa0.perex.cz (Postfix) with ESMTP id 39957244EC for ; Tue, 18 Sep 2007 16:28:36 +0200 (CEST) In-Reply-To: <46EFD955.1000601@gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Rene Herman Cc: Takashi Iwai , Krzysztof Helt , ALSA devel , Trent Piepho List-Id: alsa-devel@alsa-project.org On 09/18/2007 03:57 PM, Rene Herman wrote: Subject was supposed to be as above. > Well, if you insist, but thought I'd submit is seperately once again. > The schedule_timeout() calls in there are so-so, will simply not > schedule, but that > > while (instr->use) > schedule_timeout(1); > > loop is dangerous. There's nothing that I can see that's stopping the > compiler from turning this into an infinite loop: > > if (instr->use) > while (1) > schedule_timeout(1); > > I'll admit I have no idea where this code ends up, but if it's _ever_ > used this seems to not be good. > > Ofcourse, feel free to drop on the floor if you really do insist. > > Signed-off-by: Rene Herman Rene.