linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Kubecek <mkubecek@suse.cz>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH 1/2] netlink: add NLA_REJECT policy type
Date: Thu, 13 Sep 2018 12:49:55 +0200	[thread overview]
Message-ID: <20180913104955.GE29691@unicorn.suse.cz> (raw)
In-Reply-To: <20180913084603.7979-1-johannes@sipsolutions.net>

On Thu, Sep 13, 2018 at 10:46:02AM +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
> 
> In some situations some netlink attributes may be used for output
> only (kernel->userspace) or may be reserved for future use. It's
> then helpful to be able to prevent userspace from using them in
> messages sent to the kernel, since they'd otherwise be ignored and
> any future will become impossible if this happens.
> 
> Add NLA_REJECT to the policy which does nothing but reject (with
> EINVAL) validation of any messages containing this attribute.
> Allow for returning a specific extended ACK error message in the
> validation_data pointer.
> 
> While at it fix the indentation of NLA_BITFIELD32 and describe the
> validation_data pointer for it.
> 
> The specific case I have in mind now is a shared nested attribute
> containing request/response data, and it would be pointless and
> potentially confusing to have userspace include response data in
> the messages that actually contain a request.
> 
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> ...
> @@ -251,10 +256,13 @@ int nla_parse(struct nlattr **tb, int maxtype, const struct nlattr *head,
>  
>  		if (type > 0 && type <= maxtype) {
>  			if (policy) {
> -				err = validate_nla(nla, maxtype, policy);
> +				err = validate_nla(nla, maxtype, policy,
> +						   extack);
>  				if (err < 0) {
> -					NL_SET_ERR_MSG_ATTR(extack, nla,
> -							    "Attribute failed policy validation");
> +					NL_SET_BAD_ATTR(extack, nla);
> +					if (extack && !extack->_msg)
> +						NL_SET_ERR_MSG(extack,
> +							       "Attribute failed policy validation");
>  					goto errout;
>  				}
>  			}
> -- 

Technically, this would change the outcome when nla_parse() is called
with extack->_msg already set nad validate_nla() fails on something else
than NLA_REJECT; it will preserve the previous message in such case.
But I don't think this is a serious problem.

Reviewed-by: Michal Kubecek <mkubecek@suse.cz>

  parent reply	other threads:[~2018-09-13 15:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13  8:46 [PATCH 1/2] netlink: add NLA_REJECT policy type Johannes Berg
2018-09-13  8:46 ` [PATCH 2/2] netlink: add ethernet address policy types Johannes Berg
2018-09-13 11:58   ` Michal Kubecek
2018-09-13 12:02     ` Johannes Berg
2018-09-13 12:12       ` Michal Kubecek
2018-09-13 12:16         ` Johannes Berg
2018-09-13 12:24           ` Michal Kubecek
2018-09-13 12:46             ` Johannes Berg
2018-09-13 16:03               ` Michal Kubecek
2018-09-13 19:41           ` Marcelo Ricardo Leitner
2018-09-13 20:39             ` Michal Kubecek
2018-09-17  7:45               ` Johannes Berg
2018-09-13 10:49 ` Michal Kubecek [this message]
2018-09-13 11:25   ` [PATCH 1/2] netlink: add NLA_REJECT policy type Johannes Berg
2018-09-13 12:05     ` Michal Kubecek
2018-09-13 19:20       ` Marcelo Ricardo Leitner
2018-09-13 20:43         ` Michal Kubecek
2018-09-13 19:30 ` Marcelo Ricardo Leitner
2018-09-13 21:27   ` Michal Kubecek
2018-09-13 21:58     ` Marcelo Ricardo Leitner
2018-09-17  9:38       ` Johannes Berg
2018-09-17 20:17         ` Marcelo Ricardo Leitner
2018-09-18 12:34         ` Jamal Hadi Salim
2018-09-18 12:39           ` Johannes Berg
2018-09-18 12:55             ` Jamal Hadi Salim
2018-09-18 12:57               ` Johannes Berg
2018-09-18 13:12                 ` Jamal Hadi Salim
2018-09-18 16:42                   ` Johannes Berg
2018-09-13 22:59 ` David Miller
2018-09-17  9:39   ` 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=20180913104955.GE29691@unicorn.suse.cz \
    --to=mkubecek@suse.cz \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).