From: patchwork-bot+netdevbpf@kernel•org
To: Petr Machata <petrm@nvidia•com>
Cc: netdev@vger•kernel.org, dsahern@kernel•org, davem@davemloft•net,
kuba@kernel•org, idosch@nvidia•com
Subject: Re: [PATCH net-next v2 0/3] nexthop: More fine-grained policies for netlink message validation
Date: Thu, 21 Jan 2021 05:10:09 +0000 [thread overview]
Message-ID: <161120580957.27834.10077802568257203594.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1611156111.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 20 Jan 2021 16:44:09 +0100 you wrote:
> There is currently one policy that covers all attributes for next hop
> object management. Actual validation is then done in code, which makes it
> unobvious which attributes are acceptable when, and indeed that everything
> is rejected as necessary.
>
> In this series, split rtm_nh_policy to several policies that cover various
> aspects of the next hop object configuration, and instead of open-coding
> the validation, defer to nlmsg_parse(). This should make extending the next
> hop code simpler as well, which will be relevant in near future for
> resilient hashing implementation.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] nexthop: Use a dedicated policy for nh_valid_get_del_req()
https://git.kernel.org/netdev/net-next/c/60f5ad5e19c0
- [net-next,v2,2/3] nexthop: Use a dedicated policy for nh_valid_dump_req()
https://git.kernel.org/netdev/net-next/c/44551bff290d
- [net-next,v2,3/3] nexthop: Specialize rtm_nh_policy
https://git.kernel.org/netdev/net-next/c/643d0878e674
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-01-21 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 15:44 [PATCH net-next v2 0/3] nexthop: More fine-grained policies for netlink message validation Petr Machata
2021-01-20 15:44 ` [PATCH net-next v2 1/3] nexthop: Use a dedicated policy for nh_valid_get_del_req() Petr Machata
2021-01-21 4:26 ` David Ahern
2021-01-20 15:44 ` [PATCH net-next v2 2/3] nexthop: Use a dedicated policy for nh_valid_dump_req() Petr Machata
2021-01-21 4:27 ` David Ahern
2021-01-20 15:44 ` [PATCH net-next v2 3/3] nexthop: Specialize rtm_nh_policy Petr Machata
2021-01-21 4:29 ` David Ahern
2021-01-21 5:10 ` patchwork-bot+netdevbpf [this message]
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=161120580957.27834.10077802568257203594.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=idosch@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=petrm@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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