Return-path: Received: from www17.your-server.de ([213.133.104.17]:43760 "EHLO www17.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752568Ab0HFPym (ORCPT ); Fri, 6 Aug 2010 11:54:42 -0400 From: Thomas Meyer To: Johannes Berg Subject: Re: [PATCH 2.6.36] iwlwifi: fix locking assertions Date: Fri, 6 Aug 2010 17:12:44 +0200 Cc: John Linville , "linux-wireless" , "Wey-Yi W Guy" , "Zhao, Shanyu" References: <1281104273.3853.504.camel@jlt3.sipsolutions.net> In-Reply-To: <1281104273.3853.504.camel@jlt3.sipsolutions.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Message-Id: <201008061712.44561.thomas@m3y3r.de> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Friday 06 August 2010 16:17:53 Johannes Berg wrote: > From: Johannes Berg > > spin_is_locked() can return zero on some (UP?) Yes, this is an UP config. > configurations because locks don't exist, and > that causes an endless amount of warnings. Use > lockdep_assert_held() instead, which has two > advantages: > 1) it verifies the current task is holding > the lock or mutex > 2) it compiles away completely when lockdep > is not enabled > After applying your patch the warnings in the kernel log are gone. Thanks for the quick fix. kind regards thomas