Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp613095ybe; Wed, 11 Sep 2019 01:54:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqxmKBZMjKMxiYte0/uwAfFcUQgbrPGaCX5IwWvBH3whmgyFoJNgTdPu5eF0JlbuxHc+ryJf X-Received: by 2002:a50:99da:: with SMTP id n26mr19113675edb.293.1568192047916; Wed, 11 Sep 2019 01:54:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568192047; cv=none; d=google.com; s=arc-20160816; b=Jok7dJqd7xYgp2ztk5mjfj/d+mk18OMagFDeDw5MtaSYxyBpvAOSssR23+3FwMlrS/ PMFh36N9SD83bh1L1e2aMOwsCHwn65XNc382NmAh2xC1CThTM3gAms1CZA6QJdbMsldC aokrP/5TbWE1QMrqYFCW1GBEufZUlqwjwT8MgSq1xZLt7/9sF5Vg+u8N6Btenahy5yHR +nl+Hy6fhwmv5A04cYqnQaGMi0zqVSDHdzX4BJv912DB305IgIZxYhKg5XT+dJ/KYwBt 4l2hetutRh/a8OZqRI2ieV3dO+W0VKCgXQhX8NAs0Zb399zM3TOcTSjEJuYn2MyhF8Za hiNw== 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=SZ3MkAfn+0k27KJQqrFKsSBeI71XlNl0JxeBBVmDfTQ=; b=DlOBh4jKLLTl3ctcp9Zzg2Zrt7TKE3ZV0Ndnsw/AN5IaxCooT/RDfxvoUpS9vkRAWl e8YztK5bNrAwKijwoWEYXJUP5D9ZmEMsJVzLItHV7CQkiJ6J5rBHo3t2zYheyj+ZAhPA 1lWnKrdmWviUFsnH0fddP2LuGMb7/0DG5KRLJfehZUHpHkCfAFDVuqVQctHKTKmtAfm9 XBFu4BA9Onmja+YtiLyhQidHxl8pF83BLK+jnLIur11J4UxNrUpe3kFCybD6i/K92XLG iK1+PWF+QCFpKDb6Zxu8Moki1bk2YHZpThQoW1wf25VbRq4rAdNWqn1TemSEM2bQXWwI 7Vkw== 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 v3si11904740edc.404.2019.09.11.01.53.40; Wed, 11 Sep 2019 01:54:07 -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 S1726889AbfIKIxQ (ORCPT + 99 others); Wed, 11 Sep 2019 04:53:16 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:33708 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726579AbfIKIxQ (ORCPT ); Wed, 11 Sep 2019 04:53:16 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1i7yNG-0001tn-MX; Wed, 11 Sep 2019 10:53:14 +0200 Message-ID: <7a089d5ec94da92fc0c1255a2afa6ae0d8b8aaa4.camel@sipsolutions.net> Subject: Re: [PATCH] nl80211: Support mgmt frame unregistrations From: Johannes Berg To: Denis Kenzior , linux-wireless@vger.kernel.org Date: Wed, 11 Sep 2019 10:53:13 +0200 In-Reply-To: <20190904162239.2075-1-denkenz@gmail.com> (sfid-20190904_195856_475903_CA5D028C) References: <20190904162239.2075-1-denkenz@gmail.com> (sfid-20190904_195856_475903_CA5D028C) 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 Wed, 2019-09-04 at 11:22 -0500, Denis Kenzior wrote: > To state another way, it is > currently not possible to write a userspace application that utilizes a > single nl80211 genl socket, instead it must open multiple genl sockets > for multiple wdevs on multiple phys. I don't see how this is too onerous for the application, every application is basically going to have an event loop anyway. Thus, I don't really see any reason for us to add a bunch of code just to make an application track fewer file descriptors - we need to have the cleanup on close already anyway, so why not actually exercise those code paths? I do note that with the "unregister on iftype change" patch you could switch to an unsupported type and reach this, but I don't think you'd want to rely on that :-) Possibly I could imagine a reason for this if you needed a single socket for functional reason, but you're not really giving any such reason. I could imagine that there might be races, but I'm having a hard time coming up with a scenario where they actually matter ... if you really really get a race between e.g. RX-AUTH and INTERFACE-DEL you'll try to do some operations that will just fail, but so what? johannes