[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87fslxgx6r.fsf@toke.dk>
Date: Thu, 28 Apr 2022 15:22:04 +0200
From: Toke Høiland-Jørgensen <toke@...hat.com>
To: menglong8.dong@...il.com, edumazet@...gle.com
Cc: rostedt@...dmis.org, mingo@...hat.com, davem@...emloft.net,
yoshfuji@...ux-ipv6.org, dsahern@...nel.org, kuba@...nel.org,
pabeni@...hat.com, benbjiang@...cent.com, flyingpeng@...cent.com,
imagedong@...cent.com, kafai@...com, talalahmad@...gle.com,
keescook@...omium.org, mengensun@...cent.com,
dongli.zhang@...cle.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 2/2] net: tcp: add skb drop reasons to
route_req()
menglong8.dong@...il.com writes:
> From: Menglong Dong <imagedong@...cent.com>
>
> Add skb drop reasons to the route_req() in struct tcp_request_sock_ops.
> Following functions are involved:
>
> tcp_v4_route_req()
> tcp_v6_route_req()
> subflow_v4_route_req()
> subflow_v6_route_req()
>
> And the new reason SKB_DROP_REASON_SECURITY is added, which is used when
> skb is dropped by LSM.
Could we maybe pick a slightly less generic name? If I saw
"SKB_DROP_REASON_SECURITY" my first thought would be something related
to *network* security, like a firewall. Maybe just SKB_DROP_REASON_LSM?
-Toke
Powered by blists - more mailing lists