[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL+tcoBTzU_3Y-tMMT6iHg59oBxRUsm3JMBPMLW62LkH+AgLEg@mail.gmail.com>
Date: Wed, 14 Feb 2024 01:01:00 +0800
From: Jason Xing <kerneljasonxing@...il.com>
To: David Ahern <dsahern@...nel.org>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, kuniyu@...zon.com, netdev@...r.kernel.org,
Jason Xing <kernelxing@...cent.com>
Subject: Re: [PATCH net-next v4 3/5] tcp: use drop reasons in cookie check for ipv4
On Tue, Feb 13, 2024 at 11:56 PM David Ahern <dsahern@...nel.org> wrote:
>
> On 2/13/24 6:42 AM, Jason Xing wrote:
> > diff --git a/net/ipv4/syncookies.c b/net/ipv4/syncookies.c
> > index 38f331da6677..07e201cc3d6a 100644
> > --- a/net/ipv4/syncookies.c
> > +++ b/net/ipv4/syncookies.c
> > @@ -452,8 +456,10 @@ struct sock *cookie_v4_check(struct sock *sk, struct sk_buff *skb)
> > ireq->ir_loc_addr, th->source, th->dest, sk->sk_uid);
> > security_req_classify_flow(req, flowi4_to_flowi_common(&fl4));
> > rt = ip_route_output_key(net, &fl4);
> > - if (IS_ERR(rt))
> > + if (IS_ERR(rt)) {
> > + SKB_DR_SET(reason, IP_ROUTEOUTPUTKEY);
>
> Reason names should be based on functional failures, not function names
> which will change over time. In this case the failure is an output route
> lookup which is basically SKB_DROP_REASON_IP_OUTNOROUTES
You're right. I'll update it soon :)
Thanks,
Jason
>
>
>
Powered by blists - more mailing lists