Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp5869736ybp; Tue, 8 Oct 2019 09:27:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqzwHpV5etf3CIpuK9kwbyXi9LPQpKTo7aXGfVy0bFIV3O8JXiB6gyf8LDLAyJoSzHiOiRM+ X-Received: by 2002:a05:6402:b13:: with SMTP id bm19mr11963918edb.152.1570552061365; Tue, 08 Oct 2019 09:27:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570552061; cv=none; d=google.com; s=arc-20160816; b=wGh+MX+h1H++c+I/9q262r9wLFlWDsMMizxg9525yzs2A04L1mGt2zhpm53J9S9clg FLRcnVtW6lCZ1QU3mKD50I9l5ZSV/rQlgOsYUx14smxx1Asmhb2wJSNKiG6tb6onYyis r1dNqsNdPokN+ZNkli38Lm5ltpYWuqsXrV63jVaUJ5+IPnOcrPs5fOV91EbsYAEthJob RjXOXhWqKmtZgI+wVvbIVOgE0nNp3n4ePxui+Wl4WLqzvMNzRqGW33Td7mjieG/Kl54C P0dw6fACPsmlavLVgl4+uER2S+xFHN87R3PvR4CqJH2PkZlaDn03Xv0yFWlQK+rBDosk DUiA== 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:to:from:subject:message-id; bh=sovbiKMEDN56CSW1FahU0g6Kq/DS3qEK/pIkwIDnLAk=; b=tjuBu00VBLRDif8/Djlki9LSX3aE/9wp3visUL1jVBmfA5oO2tjQX5JgQIqbh/B4kR 9dpml0PEudMh/0t75OS57AUGFBA5pu6Auk8G8NxXsWFlHTs52G84pTPmJj+qnegH8Tc7 xO+6s0QwlcKASVLuhFmvDB94uSljMyNw8mrJVFVQvq0c+dU/0B4jDFhEhERQpZt8SNxN 4GTqnZrOWQU4dITAM3ONOh8QclNIpXgoVxQ3o13RA19whm6A56B0DbS/bAjwe1QhVtrB dnOdyZcPtBupxNyHxhZpM1YSfNS0TF/hNja6XYm8G989Q+u6pr7avMwut7ASjR50krfe g2vg== 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 b42si10675038edb.11.2019.10.08.09.27.10; Tue, 08 Oct 2019 09:27:41 -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 S1728763AbfJHQYf (ORCPT + 99 others); Tue, 8 Oct 2019 12:24:35 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:42582 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727691AbfJHQYf (ORCPT ); Tue, 8 Oct 2019 12:24:35 -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 1iHsHp-0003yI-DP; Tue, 08 Oct 2019 18:24:33 +0200 Message-ID: Subject: Re: [PATCH 2/2] mac80211: Support LIVE_ADDRESS_CHANGE feature From: Johannes Berg To: Denis Kenzior , James Prestwood , linux-wireless@vger.kernel.org Date: Tue, 08 Oct 2019 18:24:32 +0200 In-Reply-To: <864267ec-9158-940d-6e0e-db84a395888e@gmail.com> (sfid-20191008_180339_379266_C92398E9) References: <20190913195908.7871-1-prestwoj@gmail.com> <20190913195908.7871-2-prestwoj@gmail.com> <90ae00044bc0834d87d3f9fb75ce63dce4cfadd5.camel@gmail.com> <0b57c1288016310050ccd6233dda886fc4a89b02.camel@gmail.com> <6fa34e4c-5c81-4875-da29-cada1a078e2c@gmail.com> <6530a6b06176790c5a6949d6ffccf37b506975bd.camel@sipsolutions.net> <864267ec-9158-940d-6e0e-db84a395888e@gmail.com> (sfid-20191008_180339_379266_C92398E9) 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: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi, > > The scan_req struct contains a reference to which interface is scanning, > > so it should very well be possible to have > > > > phy0: > > wlan0: IFF_UP & scanning > > wlan1: IFF_UP & change MAC address all the time > > > > just like it's possible to change the MAC address when wlan1 *isn't* > > IFF_UP even if wlan0 is scanning, right? > > > > Indeed. But that is not what you were suggesting earlier with just > checking local->scanning. So if scan_req contains a wdev, then yes it > should be possible to compare the scan_req->wdev to the interface being > changed. Well, yes, but only because I was incrementally going from James's patch, which was checking that only. Similar with the other local-> things being checked here, btw, though in some cases it might be harder to actually determine which wdev is doing something and which isn't. > > No, this typically cannot be fixed, and it doesn't really make sense. > > The NIC cannot possibly do two scans at a time since it has only a > > single radio resource :-) > > So why is the scan request not per phy then? And should mac address > even affect the ongoing scan? Can we simply change it with the scan > ongoing? There are things that affect the scan from the interface, e.g. capability overrides, (extended) capabilities, the MAC address is used unless randomization is requested, etc. johannes