Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp862670pxf; Wed, 7 Apr 2021 13:34:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzbW4BBJRs6tG4oG9G46PObNbiJ31l5rejo1Mw9SkNKXgiYR2SaDHLhxd64q0GLsqJU3Haz X-Received: by 2002:a05:6402:3487:: with SMTP id v7mr6753095edc.302.1617827652607; Wed, 07 Apr 2021 13:34:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617827652; cv=none; d=google.com; s=arc-20160816; b=v3E+lHZ/B+rMFQHDR74YrsekNQq7L6zf2aFN+CBrTtIfX2wE4+F9WH3s9Z6GX2T+Tb m3YvSy0b6Cu4K5kvKkaQpiZOEj1HnPrZTVF17hysmne4i24iigNKUVR+asfVnT+8V6LP Q5TNzFNUbk0Po1T95EKjoLnzLkexES8EjzM+fSclq/BBuHOB01nOeBPj2W3dyYDJL/Jt aFIKTezqBFpkQ8D3Yii+xQLaSkwWlIlrWJqi1fQ4NJOtqwRGKXkT3jPI3lbDwdMCfgm1 uvQE+5pbaOytJY3gvIZwu/gXWcY5CSf07eYxnRDcJSMBBuOP3qEJOvfT4rPG3Go9rL7a VOeA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=Bq6eIXUckkKD83OA8LBwmG7xu3QsL4Rr/1WK+WLXbG8=; b=Ojse0CaarZIF2d76FQe3B2mIfx5GEuyJZdhREOiEYcwfEYOR+0J+jc81xslborIW19 zRAuHx+Hj96jf/0Hl7L1P41Wg7kwYAPB+qJmx1yor6J+G/X+NzMdpkiG+gqjSlQ7c5F5 NV6VVcGA7PDfqnN8H0njecK+FZKZqnYSmlIAlSGle0sn1uvyW6hJp4nmwEVKARew/8cS YfghVrkYol5U+CYxKI6SNFDGZmUiNxgD3izj6zZFRa5wOBeP/bIkxsMz3XSdUXX9+Pc1 xKsz1p3+CCfz6d6WyouQiSQljEL93wQxTSjJRlxrQEm38IqO62D5Co4IIK85ZUCR1bIa T5xA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s9si19828316edc.296.2021.04.07.13.33.49; Wed, 07 Apr 2021 13:34:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234276AbhDGH5N (ORCPT + 99 others); Wed, 7 Apr 2021 03:57:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45718 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229529AbhDGH5L (ORCPT ); Wed, 7 Apr 2021 03:57:11 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 25EEFC06174A for ; Wed, 7 Apr 2021 00:56:56 -0700 (PDT) Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.94) (envelope-from ) id 1lU33S-008Ty0-PO; Wed, 07 Apr 2021 09:56:50 +0200 Message-ID: <5c35de6e8e73fedb58e81919f465fe4038dacbbb.camel@sipsolutions.net> Subject: Re: [PATCH] iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_gen2_enqueue_hcmd() From: Johannes Berg To: Jiri Kosina , Heiner Kallweit Cc: Kalle Valo , linux-wireless Date: Wed, 07 Apr 2021 09:56:49 +0200 In-Reply-To: <95b6c4b34da1173faf226246ea25b47a8fd395b7.camel@sipsolutions.net> (sfid-20210407_095601_284772_0EEA2A3A) References: (sfid-20210407_095129_306913_82B5BB2F) <95b6c4b34da1173faf226246ea25b47a8fd395b7.camel@sipsolutions.net> (sfid-20210407_095601_284772_0EEA2A3A) Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-malware-bazaar: not-scanned Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Wed, 2021-04-07 at 09:55 +0200, Johannes Berg wrote: > On Wed, 2021-04-07 at 09:51 +0200, Jiri Kosina wrote: > > On Wed, 7 Apr 2021, Heiner Kallweit wrote: > > > > > Same fix as in 2800aadc18a6 ("iwlwifi: Fix softirq/hardirq disabling in > > > iwl_pcie_enqueue_hcmd()") is needed for iwl_pcie_gen2_enqueue_hcmd. > > > I get the same lockdep warning on AX210. > > > > Makes sense, it's being called from exactly the same contexts. > > I'm guessing nobody saw this before because the LEDs stuff is not > supported/used on newer devices :) Eh, wait, Heiner said he sees the same warning? With LEDs? I was pretty sure that's not supported by the later firmware, but maybe some other path? Anyway this fix seems right. johannes