From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [PATCH 2.6.27-rc8 5/6] e1000e: debug contention on NVM SWFLAG Date: Fri, 3 Oct 2008 21:38:44 +0200 (CEST) Message-ID: References: <20081002233314.12556.49143.stgit@jbrandeb-bw.jf.intel.com> <20081002233340.12556.33137.stgit@jbrandeb-bw.jf.intel.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Linus Torvalds , Jesse Brandeburg , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, arjan@linux.intel.com, airlied@gmail.com, davem@davemloft.net, Jeff Garzik To: Jiri Kosina Return-path: Received: from www.tglx.de ([62.245.132.106]:47639 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752475AbYJCTjP (ORCPT ); Fri, 3 Oct 2008 15:39:15 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Fri, 3 Oct 2008, Jiri Kosina wrote: > On Fri, 3 Oct 2008, Linus Torvalds wrote: > > > > The debugging message is racy anyway with respect to accessing > > > nvm_owner, right? It should be done after the mutex has been > > > succesfully acquired. > > It's done that way on purpose - to see who _could_ be racing. > > I know. I just wanted to point out that we probably don't want the patch > in 2.6.27 in this form, users wouldn't like to have warning in their logs > every time mutex is not acquired on a first attempt :) Yeah, it should go before .27 final. It now just gathers data as people actually care about warn_ons or they are even caught automatically via kernel oops. Thanks, tglx