From: Jakub Kicinski <kuba@kernel.org>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: Jiri Pirko <jiri@resnulli.us>,
johannes@sipsolutions.net, dsahern@kernel.org,
pablo@netfilter.org, netdev@vger.kernel.org
Subject: Re: Genetlink per cmd policies
Date: Wed, 30 Sep 2020 09:11:12 -0700 [thread overview]
Message-ID: <20200930091112.49c216e2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200930160303.uymslyt5isgzcl67@lion.mk-sys.cz>
On Wed, 30 Sep 2020 18:03:03 +0200 Michal Kubecek wrote:
> On Wed, Sep 30, 2020 at 08:49:55AM -0700, Jakub Kicinski wrote:
> > Hi!
> >
> > I'd like to be able to dump ethtool nl policies, but right now policy
> > dumping is only supported for "global" family policies.
> >
> > Is there any reason not to put the policy in struct genl_ops,
> > or just nobody got to it, yet?
> >
> > I get the feeling that this must have been discussed before...
>
> It used to be per-cmd but with common maxattr which didn't make much
> sense. In 5.2 cycle, commit 3b0f31f2b8c9 ("genetlink: make policy common
> to family") changed it to common policy for each family.
Interesting 🤔
next prev parent reply other threads:[~2020-09-30 16:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 15:49 Genetlink per cmd policies Jakub Kicinski
2020-09-30 16:03 ` Michal Kubecek
2020-09-30 16:11 ` Jakub Kicinski [this message]
2020-09-30 16:06 ` Johannes Berg
2020-09-30 16:17 ` Johannes Berg
2020-09-30 16:44 ` Jakub Kicinski
2020-09-30 18:36 ` Johannes Berg
2020-09-30 18:42 ` Michal Kubecek
2020-09-30 18:42 ` Johannes Berg
2020-09-30 19:01 ` Jakub Kicinski
2020-09-30 19:03 ` Johannes Berg
2020-09-30 19:14 ` Jakub Kicinski
2020-09-30 19:15 ` Johannes Berg
2020-09-30 19:46 ` Jakub Kicinski
2020-09-30 20:13 ` Johannes Berg
2020-09-30 20:47 ` Jakub Kicinski
2020-09-30 23:38 ` Andrew Lunn
2020-10-01 0:23 ` Jakub Kicinski
2020-10-01 1:53 ` Andrew Lunn
2020-10-01 15:50 ` Jakub Kicinski
2020-10-01 15:52 ` Johannes Berg
2020-09-30 16:18 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200930091112.49c216e2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=dsahern@kernel.org \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.