From: Kory Maincent <kory.maincent@bootlin.com>
To: Ido Schimmel <idosch@nvidia.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<kuba@kernel.org>, <pabeni@redhat.com>, <edumazet@google.com>,
<horms@kernel.org>, <donald.hunter@gmail.com>,
<dsahern@kernel.org>, <petrm@nvidia.com>, <gnault@redhat.com>
Subject: Re: [PATCH net-next 5/8] net: fib_rules: Enable port mask usage
Date: Tue, 18 Feb 2025 18:15:23 +0100 [thread overview]
Message-ID: <20250218181523.71926b7e@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <20250217134109.311176-6-idosch@nvidia.com>
On Mon, 17 Feb 2025 15:41:06 +0200
Ido Schimmel <idosch@nvidia.com> wrote:
> Allow user space to configure FIB rules that match on the source and
> destination ports with a mask, now that support has been added to the
> FIB rule core and the IPv4 and IPv6 address families.
>
> Reviewed-by: Petr Machata <petrm@nvidia.com>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> ---
> net/core/fib_rules.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/core/fib_rules.c b/net/core/fib_rules.c
> index ba6beaa63f44..5ddd34cbe7f6 100644
> --- a/net/core/fib_rules.c
> +++ b/net/core/fib_rules.c
> @@ -843,8 +843,8 @@ static const struct nla_policy fib_rule_policy[FRA_MAX +
> 1] = { [FRA_DSCP] = NLA_POLICY_MAX(NLA_U8, INET_DSCP_MASK >> 2),
> [FRA_FLOWLABEL] = { .type = NLA_BE32 },
> [FRA_FLOWLABEL_MASK] = { .type = NLA_BE32 },
> - [FRA_SPORT_MASK] = { .type = NLA_REJECT },
> - [FRA_DPORT_MASK] = { .type = NLA_REJECT },
> + [FRA_SPORT_MASK] = { .type = NLA_U16 },
> + [FRA_DPORT_MASK] = { .type = NLA_U16 },
> };
I don't get the purpose of this patch and patch 1.
Couldn't you have patch 3 and 4 first, then patch 2 that adds the netlink and
UAPI support?
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-02-18 17:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 13:41 [PATCH net-next 0/8] net: fib_rules: Add port mask support Ido Schimmel
2025-02-17 13:41 ` [PATCH net-next 1/8] net: fib_rules: Add port mask attributes Ido Schimmel
2025-02-17 13:41 ` [PATCH net-next 2/8] net: fib_rules: Add port mask support Ido Schimmel
2025-02-17 13:41 ` [PATCH net-next 3/8] ipv4: fib_rules: Add port mask matching Ido Schimmel
2025-02-17 13:41 ` [PATCH net-next 4/8] ipv6: " Ido Schimmel
2025-02-17 13:41 ` [PATCH net-next 5/8] net: fib_rules: Enable port mask usage Ido Schimmel
2025-02-18 17:15 ` Kory Maincent [this message]
2025-02-18 18:15 ` Ido Schimmel
2025-02-18 19:22 ` Kory Maincent
2025-02-17 13:41 ` [PATCH net-next 6/8] netlink: specs: Add FIB rule port mask attributes Ido Schimmel
2025-02-17 13:41 ` [PATCH net-next 7/8] selftests: fib_rule_tests: Add port range match tests Ido Schimmel
2025-02-17 13:41 ` [PATCH net-next 8/8] selftests: fib_rule_tests: Add port mask " Ido Schimmel
2025-02-18 12:16 ` [PATCH net-next 0/8] net: fib_rules: Add port mask support Guillaume Nault
2025-02-19 15:22 ` David Ahern
2025-02-20 2:50 ` patchwork-bot+netdevbpf
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=20250218181523.71926b7e@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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