From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail1.radix.net ([207.192.128.31]:51415 "EHLO mail1.radix.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757371AbZAQNUh (ORCPT ); Sat, 17 Jan 2009 08:20:37 -0500 Subject: Re: [linux-dvb] RFC - Flexcop Streaming watchdog (VDSB) From: Andy Walls To: Patrick Boettcher Cc: BOUWSMA Barry , lexW , Linux Media Mailing List In-Reply-To: References: <4970D464.5070509@gmx.de> Content-Type: text/plain Date: Sat, 17 Jan 2009 08:18:56 -0500 Message-Id: <1232198336.2951.13.camel@morgan.walls.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: Patrick, Please ignore my comment prior in this thread about using spin_lock_irq() vs. spin_lock_irqsave(). Between lack of sleep and trying to install Fedora 10 and recover my data on what now appears to be a failing motherboard/cpu, I made an error. I realized spinlock functions should always disable local IRQs (*smacks forehead*). What one has to take care with is unconditionally re-enabling local IRQs with spin_unlock_irq(). One would think that a work handler is known to be called in a non-irq context. So, at the risk of being wrong again, using spin_unlock_irq() should be OK, if spin_lock_irq() is allowed by the kernel in a work handler context (which your experimentation indicates that it is not). Regards, Andy