Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752068AbaDOWxg (ORCPT ); Tue, 15 Apr 2014 18:53:36 -0400 Received: from gw-1.arm.linux.org.uk ([78.32.30.217]:35736 "EHLO pandora.arm.linux.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751733AbaDOWxd (ORCPT ); Tue, 15 Apr 2014 18:53:33 -0400 Date: Tue, 15 Apr 2014 23:52:51 +0100 From: Russell King - ARM Linux To: Fabio Estevam Cc: sameo@linux.intel.com, lee.jones@linaro.org, linux-kernel@vger.kernel.org, Fabio Estevam Subject: Re: [PATCH] mfd: mc13xxx-core: Initialize the lock prior to using it Message-ID: <20140415225250.GB24070@n2100.arm.linux.org.uk> References: <1397601790-27916-1-git-send-email-festevam@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1397601790-27916-1-git-send-email-festevam@gmail.com> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 15, 2014 at 07:43:10PM -0300, Fabio Estevam wrote: > From: Fabio Estevam > > After request_threaded_irq() is called there is a chance that an interrupt > may occur before the 'mc13xxx->lock' is initialized, which will trigger a kernel > warning. I'd suggest... "which will trigger a kernel oops" because that's what you got - it killed the IRQ thread, which then caused a few other problems along the way. > In order to prevent that, move the initialization of 'mc13xxx->lock' prior to > requesting the interrupts. > > Suggested-by: Russell King > Signed-off-by: Fabio Estevam Patch looks good, and should fix the reported issue... so with the above description fixed, Acked-by: Russell King Thanks. -- FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly improving, and getting towards what was expected from it. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/