| 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
| ||
|
Date: Mon, 19 Feb 2024 13:07:56 +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 v6 07/11] tcp: add more specific possible drop reasons in tcp_rcv_synsent_state_process() On Mon, Feb 19, 2024 at 12:55 PM Kuniyuki Iwashima <kuniyu@...zon.com> wrote: > > From: Jason Xing <kerneljasonxing@...il.com> > Date: Mon, 19 Feb 2024 11:28:34 +0800 > > From: Jason Xing <kernelxing@...cent.com> > > > > This patch does two things: > > 1) add two more new reasons > > description was not updated since this patch was split. I checked that since v3 patchset the current patch has not changed. The description from my perspective is right because it truly adds two reasons in tcp_rcv_synsent_state_process(). The first series in v4: For "patch v4 [1/5]" - "patch v4 [5/5]", they correspond to "patch v6 [1/11]" - "patch v6 [5/11]". The other series in v4: For "patch v4 [1/6]" - "patch v4 [6/6]", they correspond to "patch v6 [6/11]" - "patch v6 [11/11]". > > > > 2) only change the return value(1) to various drop reason values > > for the future use > > > > For now, we still cannot trace those two reasons. We'll implement the full > > function in the subsequent patch in this serie. > > > > Signed-off-by: Jason Xing <kernelxing@...cent.com>
Powered by blists - more mailing lists