From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0FCC0C10F11 for ; Sat, 13 Apr 2019 18:24:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C332E2084E for ; Sat, 13 Apr 2019 18:24:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="jqSZcqEm" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727042AbfDMSYp (ORCPT ); Sat, 13 Apr 2019 14:24:45 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:60485 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726620AbfDMSYp (ORCPT ); Sat, 13 Apr 2019 14:24:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=evg4LCaScRngBDBWn08cRk6fu6d/pZs8v2dtxp/uZ44=; b=jqSZcqEm83b7EkkJkCqH/fOXKr qyWXt4A4guwh1FB4l+7z8DcStmcP8LmA0lWt/ej+yST9BfVrbM3VUolXMiwIfNo0WshIPDi1j/P8X 4Vsl3vmGvX/QM734RUDSZV6O+tpTKweCQP9RHYumS4ntoUvjd+8p3u7DoK8bC/r7oO4s=; Received: from andrew by vps0.lunn.ch with local (Exim 4.89) (envelope-from ) id 1hFNKR-0006Zt-BL; Sat, 13 Apr 2019 20:24:39 +0200 Date: Sat, 13 Apr 2019 20:24:39 +0200 From: Andrew Lunn To: Igor Russkikh Cc: "David S . Miller" , "netdev@vger.kernel.org" , Nikita Danilov , Dmitry Bogdanov Subject: Re: [PATCH netnext 12/16] net: aquantia: wrap fw ops by mutex Message-ID: <20190413182439.GS17901@lunn.ch> References: <4c9a8c7d1771b61627beb917bd0da64d5f485aa5.1555158087.git.igor.russkikh@aquantia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4c9a8c7d1771b61627beb917bd0da64d5f485aa5.1555158087.git.igor.russkikh@aquantia.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Sat, Apr 13, 2019 at 12:32:11PM +0000, Igor Russkikh wrote: > From: Nikita Danilov > > Since fw ops may be invoked from different threads all its invocation > must be wrapped by mutex. Do all fw ops go through hw_atl_utils_fw_rpc_wait()? My experience with the mv88e6xxx driver is that you forget a lock somewhere. So we added code in the low level register access to check the lock has been taken: if (unlikely(!mutex_is_locked(&chip->reg_lock))) { dev_err(chip->dev, "Switch registers lock not held!\n"); dump_stack(); } Andrew