Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp8145551ybn; Tue, 1 Oct 2019 04:02:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqzRxjcBfmVVhn3ZA/zL1OQM5xzwTO3qRXK+LBq9OcMSnLUvD/hxoqpKpyjSHMDSAjCVRr4O X-Received: by 2002:aa7:d698:: with SMTP id d24mr7023578edr.32.1569927728911; Tue, 01 Oct 2019 04:02:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569927728; cv=none; d=google.com; s=arc-20160816; b=fNLLOulbeUnYEkahduPSiRZiszNsI9+iHm07DIgWdn5sURnS3ou0ME4VKM75H1MzEZ iA/fvZKzEsd8AAWaAsyfg8huQWphM+EhOGV7uNr5fzwtNvH4IKW6ewEMxRTUYqqcKsU9 EKmqWR0hKq7r2JmDmTU5jKH1HmNPFednuRvhKxxwLmNo8yY1GVhgjr09E65Y6y2thQJJ 4FgQpTlWu5FPPvKd/F+VEA+XSRtKY+OrRTBafO0AwOP66s/ePWnfRuddOGJ7X3wFiT3L lpzBEqpPb1bMcWGC3Sb3oXsQxSoF7rotK6547f71lW8t/A+JFdlVOQCBFtsXyZCnY0eI PYAg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=iSTJ0m/S6G27JyHeZ8WfGA/Y3J2D8V1flS4TRnybhME=; b=v47te7J2dlkUwI5WumGSTIrGKeX7lqzyApaORJPZqe+j+4bu2vciAn/XJqmq12SfbQ GxoT7LqzP+geg9Wb6aWu0RA1mve8uzH7nkwhtapxo0bge1Egq/ZAfdiE3KLcGTiHEq9Q 5SaM5Kuy/wBwvV+m9wUZqy6fh/NFcmOde3ldENsJ4+iKLjDMvAd7TxguOj/O22DD5PZ/ cdnvq7d597jjuFlBowhgwiY2mRIXZImsIOs7WG6UeOI+fIgGZwYO1FAMkvrIvE8c3Lav h5mkyEV3lCgLfchsXTvxDrBTt03mWIkynnvzP8JXZGWBOO8DsJevSSraIRsXiL0hieCF RBNQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w20si9308074edc.202.2019.10.01.04.01.44; Tue, 01 Oct 2019 04:02:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726748AbfJALBR (ORCPT + 99 others); Tue, 1 Oct 2019 07:01:17 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:59740 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725865AbfJALBR (ORCPT ); Tue, 1 Oct 2019 07:01:17 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.92.2) (envelope-from ) id 1iFFu5-00064U-9Y; Tue, 01 Oct 2019 13:01:13 +0200 Message-ID: <5bbc9f7d3a01cd578cbf894469734d88c8f59279.camel@sipsolutions.net> Subject: Re: [PATCH] mac80211: keep BHs disabled while calling drv_tx_wake_queue() From: Johannes Berg To: Jiri Kosina , Toke =?ISO-8859-1?Q?H=F8iland-J=F8rgensen?= Cc: linux-wireless@vger.kernel.org, Aaron Hill , Lukas Redlinger , Oleksii Shevchuk Date: Tue, 01 Oct 2019 13:01:12 +0200 In-Reply-To: References: <1569924485-I3e8838c5ecad878e59d4a94eb069a90f6641461a@changeid> <87blv0visz.fsf@toke.dk> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Tue, 2019-10-01 at 12:56 +0200, Jiri Kosina wrote: > On Tue, 1 Oct 2019, Toke Høiland-Jørgensen wrote: > > > > - spin_unlock_bh(&fq->lock); > > > + spin_unlock(&fq->lock); > > > drv_wake_tx_queue(local, txqi); > > > - spin_lock_bh(&fq->lock); > > > + spin_lock(&fq->lock); > > > > Okay, so this will mean that the drv_wake_tx_queue() entry point will be > > called with bhs disabled. But there are lots of uses of > > spin_{,un}lock_bh() in tx.c: > > I am fine with whatever fix for this you guys settle on :) Just for the > record, I proposed this back then: > > http://lore.kernel.org/r/nycvar.YFH.7.76.1904151300160.9803@cbobk.fhfr.pm > > maybe it could be resurected, as I believe it'd fix this one as well? Yes, it would, but it wouldn't address any other driver that likely has the same issue :) johannes