Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp2503732ybp; Thu, 10 Oct 2019 08:18:59 -0700 (PDT) X-Google-Smtp-Source: APXvYqwWplkg99mG1XpDJUg4RsLbTxH7N/WUwdzUqITbIrHeNDvR2KQiouM1qvL84SCjziVaWIrZ X-Received: by 2002:a17:906:3f87:: with SMTP id b7mr8554054ejj.107.1570720739211; Thu, 10 Oct 2019 08:18:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570720739; cv=none; d=google.com; s=arc-20160816; b=BI229yd+V3fTEthZGHOeYNpsMC07QeTnmv6Ym6JkbZUtDJBCw9t6QU05FRHdDZlwM3 JWfYIt5+wX031+iI8LKr1RoBe7lfV/6BXhV83jPcZnVoyivYQp65OXn2Bcm0bbKFnvV5 b9PlkxGuDave2OEnpsqAUibzasj4WigKnuOkyiVLWV8vV5uOUfkEhe/ktlrwO1cbfKdx o4iyLUAWFkyxpRnnp4bNPFgrUKvYFPqF5vfxRDO4Bq6oQYX4Q6TXsVljbOcxhe8e68+r QcdVMjRxA8psW57gmZl16MPVtjLIFhGkKlafNksFKUk3JSG1QSliiLXtNSLKDHsuY33H cF6w== 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=MT5OLg7zaaANAH4jwLrOWyr+MCQhd11I8m0FJpihrLo=; b=lGK9l3cfBHL2Q/QPnqKzg2JiEnjKyEmBwC3L6Q46i/Bo7IFEdwifGaJQ1wV3ATlnxB HCtJxJVkjGebvEXequWdkQ6B4aioXqEXcNaScsYXKrV3zPetSIJHvBzH6AVvBgEzMd7W +Of+l6OvG14FyyaWcvcQTRsXtJ13conDJOckKMl0ijjKD91jHcf9L31ykO+r6A7S2aG8 KVCWeSpTohVbiHFRoL552CMRZ2RysX1VF7I6r9k3cDGJcn6R+Avl2Gw9+ElTeBuWQZxH B3dllcaq4BVMmQiBE6wf7fDWfJMV39IE9HEWk8O9IxmYMP3xq/px8arH45d168l7Gi38 ocLA== 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 10si3265931ejw.231.2019.10.10.08.18.23; Thu, 10 Oct 2019 08:18:59 -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 S1726521AbfJJPSF (ORCPT + 99 others); Thu, 10 Oct 2019 11:18:05 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:42124 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725959AbfJJPSF (ORCPT ); Thu, 10 Oct 2019 11:18:05 -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 1iIaCZ-000734-Ae; Thu, 10 Oct 2019 17:18:03 +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: Thu, 10 Oct 2019 17:18:02 +0200 In-Reply-To: (sfid-20191008_225601_596382_1D893268) 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> <1bb5450b-bc4e-8c83-f99e-fc7e739b08f0@gmail.com> <193168d4-6466-60a4-bc89-c4a44e84ac46@gmail.com> <9c49ec27489333d7f27831de19e9d1c9cd65eeee.camel@sipsolutions.net> (sfid-20191008_225601_596382_1D893268) 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 On Tue, 2019-10-08 at 15:55 -0500, Denis Kenzior wrote: > Right, so you're talking in the context of this implementation which > performs a remove/add interface. You're right about that. > > But I was asking more in general terms. If all we're doing is scanning, > can we just change the mac? Anyway, not important. Maybe I bring this > up once this set is accepted. Maybe, but honestly, I'm not convinced the complexity would be worth it. You'd have to push this all the way through to the driver, so it knows to do it, or defer it until the scan is done, or something? Not something you'd want to do on all hardware while a non-randomized scan is running, for example (iwlwifi might actually be OK). Or you could perhaps cache the MAC address change in mac80211 and apply it at the next possible point in time - but then again you have to be really careful to actually apply it and block all further operations, even if a bunch of remain-on-channel's are active and you request a new scan, that has to be blocked until the remain-on-channel is done *and* the MAC address change is applied? Seems rather complex for very little value. johannes