[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL+tcoA-2ZtLxtLmmXYaX-27MeBf01eK+4zs5KEU6V3qKbGJhA@mail.gmail.com>
Date: Sat, 24 Feb 2024 08:01:57 +0800
From: Jason Xing <kerneljasonxing@...il.com>
To: Kuniyuki Iwashima <kuniyu@...zon.com>
Cc: davem@...emloft.net, dsahern@...nel.org, edumazet@...gle.com,
kernelxing@...cent.com, kuba@...nel.org, netdev@...r.kernel.org,
pabeni@...hat.com
Subject: Re: [PATCH net-next v9 06/10] tcp: introduce dropreasons in receive path
On Sat, Feb 24, 2024 at 3:33 AM Kuniyuki Iwashima <kuniyu@...zon.com> wrote:
>
> From: Jason Xing <kerneljasonxing@...il.com>
> Date: Fri, 23 Feb 2024 18:28:47 +0800
> > From: Jason Xing <kernelxing@...cent.com>
> >
> > Soon later patches can use these relatively more accurate
> > reasons to recognise and find out the cause.
> >
> > Signed-off-by: Jason Xing <kernelxing@...cent.com>
> > Reviewed-by: Eric Dumazet <edumazet@...gle.com>
> > Reviewed-by: David Ahern <dsahern@...nel.org>
>
> Reviewed-by: Kuniyuki Iwashima <kuniyu@...zon.com>
>
> one nit below.
>
> > --
> > v9
> > Link: https://lore.kernel.org/netdev/c5640fc4-16dc-4058-97c6-bd84bae4fda1@kernel.org/
> > Link: https://lore.kernel.org/netdev/CANn89i+j55o_1B2SV56n=u=NHukmN_CoRib4VBzpUBVcKRjAMw@mail.gmail.com/
> > 1. add reviewed-by tag (David)
> > 2. add reviewed-by tag (Eric)
> >
> > v7
> > Link: https://lore.kernel.org/all/20240219044744.99367-1-kuniyu@amazon.com/
> > 1. nit: nit: s/. because of/ because/ (Kuniyuki)
> >
> > v5:
> > Link: https://lore.kernel.org/netdev/3a495358-4c47-4a9f-b116-5f9c8b44e5ab@kernel.org/
> > 1. Use new name (TCP_ABORT_ON_DATA) for readability (David)
> > 2. change the title of this patch
> > ---
> > include/net/dropreason-core.h | 15 ++++++++++++++-
> > 1 file changed, 14 insertions(+), 1 deletion(-)
> >
> > diff --git a/include/net/dropreason-core.h b/include/net/dropreason-core.h
> > index a871f061558d..af7c7146219d 100644
> > --- a/include/net/dropreason-core.h
> > +++ b/include/net/dropreason-core.h
> > @@ -30,6 +30,7 @@
> > FN(TCP_AOFAILURE) \
> > FN(SOCKET_BACKLOG) \
> > FN(TCP_FLAGS) \
> > + FN(TCP_ABORT_ON_DATA) \
>
> One more trailing tab ?
Well, I noticed that there are no specific/accurate rules about adding
a trailing tab prior to the current change. Some added more than one,
some not.
>
>
> > FN(TCP_ZEROWINDOW) \
> > FN(TCP_OLD_DATA) \
> > FN(TCP_OVERWINDOW) \
> > @@ -37,6 +38,7 @@
> > FN(TCP_RFC7323_PAWS) \
> > FN(TCP_OLD_SEQUENCE) \
> > FN(TCP_INVALID_SEQUENCE) \
> > + FN(TCP_INVALID_ACK_SEQUENCE) \
> > FN(TCP_RESET) \
> > FN(TCP_INVALID_SYN) \
> > FN(TCP_CLOSE) \
> > @@ -204,6 +206,11 @@ enum skb_drop_reason {
> > SKB_DROP_REASON_SOCKET_BACKLOG,
> > /** @SKB_DROP_REASON_TCP_FLAGS: TCP flags invalid */
> > SKB_DROP_REASON_TCP_FLAGS,
> > + /**
> > + * @SKB_DROP_REASON_TCP_ABORT_ON_DATA: abort on data, corresponding to
> > + * LINUX_MIB_TCPABORTONDATA
> > + */
> > + SKB_DROP_REASON_TCP_ABORT_ON_DATA,
> > /**
> > * @SKB_DROP_REASON_TCP_ZEROWINDOW: TCP receive window size is zero,
> > * see LINUX_MIB_TCPZEROWINDOWDROP
> > @@ -228,13 +235,19 @@ enum skb_drop_reason {
> > SKB_DROP_REASON_TCP_OFOMERGE,
> > /**
> > * @SKB_DROP_REASON_TCP_RFC7323_PAWS: PAWS check, corresponding to
> > - * LINUX_MIB_PAWSESTABREJECTED
> > + * LINUX_MIB_PAWSESTABREJECTED, LINUX_MIB_PAWSACTIVEREJECTED
> > */
> > SKB_DROP_REASON_TCP_RFC7323_PAWS,
> > /** @SKB_DROP_REASON_TCP_OLD_SEQUENCE: Old SEQ field (duplicate packet) */
> > SKB_DROP_REASON_TCP_OLD_SEQUENCE,
> > /** @SKB_DROP_REASON_TCP_INVALID_SEQUENCE: Not acceptable SEQ field */
> > SKB_DROP_REASON_TCP_INVALID_SEQUENCE,
> > + /**
> > + * @SKB_DROP_REASON_TCP_INVALID_ACK_SEQUENCE: Not acceptable ACK SEQ
> > + * field because ack sequence is not in the window between snd_una
> > + * and snd_nxt
> > + */
> > + SKB_DROP_REASON_TCP_INVALID_ACK_SEQUENCE,
> > /** @SKB_DROP_REASON_TCP_RESET: Invalid RST packet */
> > SKB_DROP_REASON_TCP_RESET,
> > /**
> > --
> > 2.37.3
Powered by blists - more mailing lists