All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Cc: David Ahern <dsa@cumulusnetworks.com>,
	Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [PATCH 0/6] netlink: expose policies to userspace
Date: Fri, 26 Apr 2019 14:13:00 +0200	[thread overview]
Message-ID: <20190426121306.10871-1-johannes@sipsolutions.net> (raw)

Make some cleanups in policy validation, and add tools to expose
the policies to userspace.

This lets userspace discover what the appropriate data for an
element is.

Note that NLA_UNSPEC items are omitted as they're rejected in
strict validation mode so their policy entries should be changed
to NLA_MIN_LEN - this is just a representation change.

Eventually, I'd like to add a separation between input and output
policies (currently only the input policy is exposed), but that
needs some extra work to add "overrides".

johannes



             reply	other threads:[~2019-04-26 12:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 12:13 Johannes Berg [this message]
2019-04-26 12:13 ` [PATCH 1/6] netlink: remove type-unsafe validation_data pointer Johannes Berg
2019-04-26 12:13 ` [PATCH 2/6] netlink: extend policy range validation Johannes Berg
2019-04-30  2:49   ` David Miller
2019-04-30  6:51     ` Johannes Berg
2019-04-26 12:13 ` [PATCH 3/6] netlink: allow NLA_MSECS to have " Johannes Berg
2019-04-26 12:13 ` [PATCH 4/6] netlink: remove NLA_EXACT_LEN_WARN Johannes Berg
2019-04-26 12:13 ` [PATCH 5/6] netlink: factor out policy range helpers Johannes Berg
2019-04-26 12:13 ` [PATCH 6/6] netlink: add infrastructure to expose policies to userspace Johannes Berg
2019-04-26 18:21   ` Pablo Neira Ayuso
2019-04-26 19:22     ` Johannes Berg
2019-04-27 11:25       ` Pablo Neira Ayuso
2019-04-28 20:03         ` Johannes Berg

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=20190426121306.10871-1-johannes@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=dsa@cumulusnetworks.com \
    --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.