From patchwork Fri Oct 2 09:09:39 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Johannes Berg X-Patchwork-Id: 1375614 Return-Path: X-Original-To: patchwork-incoming-netdev@ozlabs.org Delivered-To: patchwork-incoming-netdev@ozlabs.org Authentication-Results: ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=vger.kernel.org (client-ip=23.128.96.18; helo=vger.kernel.org; envelope-from=netdev-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=none (p=none dis=none) header.from=sipsolutions.net Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by ozlabs.org (Postfix) with ESMTP id 4C2kj84GLjz9sSC for ; Fri, 2 Oct 2020 19:10:04 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387680AbgJBJJ4 (ORCPT ); Fri, 2 Oct 2020 05:09:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33646 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726398AbgJBJJ4 (ORCPT ); Fri, 2 Oct 2020 05:09:56 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3839CC0613D0 for ; Fri, 2 Oct 2020 02:09:56 -0700 (PDT) Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.94) (envelope-from ) id 1kOH4a-00F9QD-Rk; Fri, 02 Oct 2020 11:09:52 +0200 From: Johannes Berg To: netdev@vger.kernel.org Cc: Jakub Kicinski Subject: [PATCH 0/5] genetlink: complete policy dumping Date: Fri, 2 Oct 2020 11:09:39 +0200 Message-Id: <20201002090944.195891-1-johannes@sipsolutions.net> X-Mailer: git-send-email 2.26.2 MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hi, So ... Jakub added per-op policy retrieval, so you could retrieve the policy for a single op. This then adds - as discussed - support for dumping *everything*, which has basically first an [op] -> [policy-idx] mapping, followed by all the policies. When a single op is requested, you get a convenience [op] -> 0 mapping entry, but you might as well ignore it since the policy for the requested op is guaranteed to be 0. This series applies on top of Jakub's series, but I've fixed up his to apply on top of my bugfix (let me know how you want to handle that). For convenience, I've pushed the entire series here: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git/log/?h=genetlink-op-policy-export (I hope the cache will be invalidated soon, but anyway, in mac80211-next genetlink-op-policy-export branch) I didn't want to repost Jakub's slightly modified patches just for that. Depending on how we decide to deal with the conflicts, we may or may not need that series. johannes