Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2974059imu; Sun, 9 Dec 2018 14:03:32 -0800 (PST) X-Google-Smtp-Source: AFSGD/XDhLYo4SpX5ZvnKjIUIvdpXZn6GZ/fyqJzfJsTN6zSYw8gI9rknECgaCDaIr3lKGMBkZ3C X-Received: by 2002:a63:ed15:: with SMTP id d21mr8723103pgi.305.1544393012733; Sun, 09 Dec 2018 14:03:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544393012; cv=none; d=google.com; s=arc-20160816; b=RCSL24WSBXoz1rBpkxXlbkXZCcZq1EDG/KKb3S+XrHOD6fxjYh3qojqjoAGSmMUuDK Uvg4l7pPuV4dgCoHHK7yiRRLq1xdis8uzHqUnXV8KtzVBycVyYKrRdKd3r+tjeTwYoV+ tJqA3hHV8QxCQ7NUK3CkOxzKN1Vk8HsTFMRCzhiHwXFeLmpUcTazHIJ8/dXzEIkaZ6wI ZWdgboVKlKDFD6zFOHHPQD6Vz8qI1QLMQk/TFfKOcCuB11QcbE84UJYgPA3ZzeBx0qlT i+8ejjTZaxfKzPuJo6LbGmnflwqiIB2AIiRtehBZPSe2Ug0IE0SGh2SjB//IF4iULv+O 9HJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition; bh=dUnnChR8nmeLUQAZdtVm1Bzs0ZofaAjPR2Bsp+k2xdI=; b=AhBWIsUQioqjTFoedM4mVDPQeC2EMuQun64+UXTNmS7cVL/YzTehSKz40jvh6RHs9E UDNjcsWS9HbrWh3CQql+pj0RZQ2niBrvtNarH/82TaM45MB4IrWPDdlKIw9wRZDLybUN 9i9wBDHPljsbrM+puNQ/ql/zzTAmlkxsH9mlGYttbJmDkdzE3cqa2udW5D2A5/urQmnE 4wUklSu5AfVeAPB5gmACg69hWHudfh+OjQooOENv6nbLUKcLciSKvkcq62CkBFcnzunk KL8giAPQUxd0/29VzJNAQRBytq96SD69vQuvcLMEgRDQUJ5/EkmaWUK9f2YAITUB9EEN ga7w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-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 k6si8578840pla.350.2018.12.09.14.03.17; Sun, 09 Dec 2018 14:03:32 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-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-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726690AbeLIVzd (ORCPT + 99 others); Sun, 9 Dec 2018 16:55:33 -0500 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:34870 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726437AbeLIVzP (ORCPT ); Sun, 9 Dec 2018 16:55:15 -0500 Received: from pub.yeoldevic.com ([81.174.156.145] helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gW72e-0002iY-Kk; Sun, 09 Dec 2018 21:55:12 +0000 Received: from ben by deadeye with local (Exim 4.91) (envelope-from ) id 1gW72b-0003KJ-EE; Sun, 09 Dec 2018 21:55:09 +0000 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, "Sven Eckelmann" , "Kalle Valo" Date: Sun, 09 Dec 2018 21:50:33 +0000 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) X-Patchwork-Hint: ignore Subject: [PATCH 3.16 089/328] ath10k: prevent active scans on potential unusable channels In-Reply-To: X-SA-Exim-Connect-IP: 81.174.156.145 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.62-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Sven Eckelmann commit 3f259111583801013cb605bb4414aa529adccf1c upstream. The QCA4019 hw1.0 firmware 10.4-3.2.1-00050 and 10.4-3.5.3-00053 (and most likely all other) seem to ignore the WMI_CHAN_FLAG_DFS flag during the scan. This results in transmission (probe requests) on channels which are not "available" for transmissions. Since the firmware is closed source and nothing can be done from our side to fix the problem in it, the driver has to work around this problem. The WMI_CHAN_FLAG_PASSIVE seems to be interpreted by the firmware to not scan actively on a channel unless an AP was detected on it. Simple probe requests will then be transmitted by the STA on the channel. ath10k must therefore also use this flag when it queues a radar channel for scanning. This should reduce the chance of an active scan when the channel might be "unusable" for transmissions. Fixes: e8a50f8ba44b ("ath10k: introduce DFS implementation") Signed-off-by: Sven Eckelmann Signed-off-by: Kalle Valo Signed-off-by: Ben Hutchings --- drivers/net/wireless/ath/ath10k/mac.c | 7 +++++++ 1 file changed, 7 insertions(+) --- a/drivers/net/wireless/ath/ath10k/mac.c +++ b/drivers/net/wireless/ath/ath10k/mac.c @@ -1724,6 +1724,13 @@ static int ath10k_update_channel_list(st passive = channel->flags & IEEE80211_CHAN_NO_IR; ch->passive = passive; + /* the firmware is ignoring the "radar" flag of the + * channel and is scanning actively using Probe Requests + * on "Radar detection"/DFS channels which are not + * marked as "available" + */ + ch->passive |= ch->chan_radar; + ch->freq = channel->center_freq; ch->min_power = 0; ch->max_power = channel->max_power * 2;