Netdev List
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	xiyou.wangcong@gmail.com, dsahern@gmail.com,
	eric.dumazet@gmail.com, mrv@mojatatu.com,
	simon.horman@netronome.com, alex.aring@gmail.com
Subject: Re: [PATCH net-next v11 1/4] net netlink: Add new type NLA_BITFIELD_32
Date: Mon, 24 Jul 2017 13:18:06 +0200	[thread overview]
Message-ID: <20170724111806.GB1868@nanopsycho> (raw)
In-Reply-To: <1500860146-26970-2-git-send-email-jhs@emojatatu.com>

Mon, Jul 24, 2017 at 03:35:43AM CEST, jhs@mojatatu.com wrote:
>From: Jamal Hadi Salim <jhs@mojatatu.com>
>
>Generic bitflags attribute content sent to the kernel by user.
>With this type the user can either set or unset a flag in the
>kernel.
>
>The nla_value is a bitmap that defines the values being set
>The nla_selector is a bitmask that defines which value is legit.
>
>A check is made to ensure the rules that a kernel subsystem always
>conforms to bitflags the kernel already knows about. i.e
>if the user tries to set a bit flag that is not understood then
>the _it will be rejected_.
>
>In the most basic form, the user specifies the attribute policy as:
>[ATTR_GOO] = { .type = NLA_BITFIELD_32, .validation_data = &myvalidflags },
>
>where myvalidflags is the bit mask of the flags the kernel understands.
>
>If the user _does not_ provide myvalidflags then the attribute will
>also be rejected.
>
>Examples:
>nla_value = 0x0, and nla_selector = 0x1
>implies we are selecting bit 1 and we want to set its value to 0.
>
>nla_value = 0x2, and nla_selector = 0x2
>implies we are selecting bit 2 and we want to set its value to 1.

Oh, 2 more things:

[...]


>@@ -46,6 +60,13 @@ static int validate_nla(const struct nlattr *nla, int maxtype,
> 			return -ERANGE;
> 		break;
> 
>+	case NLA_BITFIELD_32:

Now that I'm looking at it, perhaps just "NLA_BITFIELD32" looks nicer
and aligns with "NLA_U32" and others.



>+		if (attrlen != sizeof(struct nla_bitfield_32))
>+			return -ERANGE;
>+
>+		return validate_nla_bitfield_32(nla, pt->validation_data);
>+		break;

Remove the pointless "break" from here.

  parent reply	other threads:[~2017-07-24 11:18 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24  1:35 [PATCH net-next v11 0/4] net sched actions: improve dump performance Jamal Hadi Salim
2017-07-24  1:35 ` [PATCH net-next v11 1/4] net netlink: Add new type NLA_BITFIELD_32 Jamal Hadi Salim
2017-07-24 11:14   ` Jiri Pirko
2017-07-25 11:14     ` Jamal Hadi Salim
2017-07-24 11:18   ` Jiri Pirko [this message]
2017-07-25 11:15     ` Jamal Hadi Salim
2017-07-25 14:41   ` David Ahern
2017-07-28 13:51     ` Jamal Hadi Salim
2017-07-28 14:08       ` Jiri Pirko
2017-07-28 14:19       ` David Ahern
2017-07-28 14:55         ` Jiri Pirko
2017-07-28 15:04         ` Jamal Hadi Salim
2017-07-28 15:13           ` David Ahern
2017-07-28 21:55             ` Jamal Hadi Salim
2017-07-24  1:35 ` [PATCH net-next v11 2/4] net sched actions: Use proper root attribute table for actions Jamal Hadi Salim
2017-07-24  1:35 ` [PATCH net-next v11 3/4] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch Jamal Hadi Salim
2017-07-24 11:27   ` Jiri Pirko
2017-07-25 11:22     ` Jamal Hadi Salim
2017-07-25 11:33       ` Jiri Pirko
2017-07-25 12:34         ` Jamal Hadi Salim
2017-07-25 12:37           ` Jiri Pirko
2017-07-28 13:41             ` Jamal Hadi Salim
2017-07-28 14:12               ` Jiri Pirko
2017-07-28 14:52                 ` Jamal Hadi Salim
2017-07-28 14:57                   ` Jiri Pirko
2017-07-28 15:08                   ` Jamal Hadi Salim
2017-07-28 15:45                     ` Jiri Pirko
2017-07-28 22:10                       ` Jamal Hadi Salim
2017-07-29  7:19                         ` Jiri Pirko
2017-07-29 11:21                           ` Jamal Hadi Salim
2017-07-24  1:35 ` [PATCH net-next v11 4/4] net sched actions: add time filter for action dumping Jamal Hadi Salim
2017-07-24 11:34   ` Jiri Pirko
2017-07-25 11:27     ` Jamal Hadi Salim
2017-07-25 11:34       ` Jiri Pirko

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=20170724111806.GB1868@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=mrv@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=simon.horman@netronome.com \
    --cc=xiyou.wangcong@gmail.com \
    /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