netdev - Re: [PATCH iproute2-next] tc: m_tunnel_key: support code for "nofrag" tunnels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <cc73004c-9aa8-9cd3-b46e-443c0727c34d@kernel.org>
Date:   Fri, 7 Apr 2023 09:40:43 -0600
From:   David Ahern <dsahern@...nel.org>
To:     Davide Caratti <dcaratti@...hat.com>,
        Jamal Hadi Salim <jhs@...atatu.com>,
        Cong Wang <xiyou.wangcong@...il.com>,
        Jiri Pirko <jiri@...nulli.us>,
        Ilya Maximets <i.maximets@....org>
Cc:     netdev@...r.kernel.org, Pedro Tammela <pctammela@...atatu.com>
Subject: Re: [PATCH iproute2-next] tc: m_tunnel_key: support code for "nofrag"
 tunnels

On 3/31/23 10:49 AM, Davide Caratti wrote:
> add control plane for setting TCA_TUNNEL_KEY_NO_FRAG flag on
> act_tunnel_key actions.
> 
> Signed-off-by: Davide Caratti <dcaratti@...hat.com>
> ---
>  include/uapi/linux/tc_act/tc_tunnel_key.h |  1 +
>  man/man8/tc-tunnel_key.8                  |  3 ++
>  tc/m_tunnel_key.c                         | 48 +++++++++++++++++------
>  3 files changed, 41 insertions(+), 11 deletions(-)
> 
> diff --git a/include/uapi/linux/tc_act/tc_tunnel_key.h b/include/uapi/linux/tc_act/tc_tunnel_key.h
> index 49ad4033951b..37c6f612f161 100644
> --- a/include/uapi/linux/tc_act/tc_tunnel_key.h
> +++ b/include/uapi/linux/tc_act/tc_tunnel_key.h
> @@ -34,6 +34,7 @@ enum {
>  					 */
>  	TCA_TUNNEL_KEY_ENC_TOS,		/* u8 */
>  	TCA_TUNNEL_KEY_ENC_TTL,		/* u8 */
> +	TCA_TUNNEL_KEY_NO_FRAG,		/* flag */
>  	__TCA_TUNNEL_KEY_MAX,
>  };
>  

applied to iproute2-next.

In the future, please make uapi changes a separate patch. UAPI headers
are synched by scripts. Inclusion in a PR is a convenience for others;
they are always dropped before applying. A separate patch makes that
process easier.