linux-kernel - Re: [PATCH net-next 00/19] net: add skb drop reasons for TCP, IP, dev and neigh

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 16 Feb 2022 09:55:34 +0800
From:   Menglong Dong <menglong8.dong@...il.com>
To:     David Ahern <dsahern@...nel.org>
Cc:     Jakub Kicinski <kuba@...nel.org>,
        Eric Dumazet <edumazet@...gle.com>,
        David Miller <davem@...emloft.net>,
        Steven Rostedt <rostedt@...dmis.org>,
        Ingo Molnar <mingo@...hat.com>,
        Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
        Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>, hawk@...nel.org,
        John Fastabend <john.fastabend@...il.com>,
        Menglong Dong <imagedong@...cent.com>,
        Talal Ahmad <talalahmad@...gle.com>,
        Kees Cook <keescook@...omium.org>, ilias.apalodimas@...aro.org,
        Alexander Lobakin <alobakin@...me>,
        Kumar Kartikeya Dwivedi <memxor@...il.com>,
        atenart@...nel.org, bigeasy@...utronix.de,
        Paolo Abeni <pabeni@...hat.com>, linyunsheng@...wei.com,
        arnd@...db.de, yajun.deng@...ux.dev,
        Roopa Prabhu <roopa@...dia.com>,
        Willem de Bruijn <willemb@...gle.com>, vvs@...tuozzo.com,
        Cong Wang <cong.wang@...edance.com>, luiz.von.dentz@...el.com,
        LKML <linux-kernel@...r.kernel.org>,
        netdev <netdev@...r.kernel.org>, bpf <bpf@...r.kernel.org>,
        flyingpeng@...cent.com
Subject: Re: [PATCH net-next 00/19] net: add skb drop reasons for TCP, IP, dev
 and neigh

On Wed, Feb 16, 2022 at 12:09 AM David Ahern <dsahern@...nel.org> wrote:
>
> On 2/15/22 9:04 AM, Jakub Kicinski wrote:
> > There's no reason to send 19 patches at a time. Please try to send
> > smaller series, that's are easier to review, under 10 patches
> > preferably, certainly under 15.
>
> +1. It takes time to review code paths and make sure the changes are
> correct.
>
> Send the first 9 as set; those target the TCP stack and then wait for
> them to be merged before sending more.

Ok, I'll make the amount of patches at a proper level, thanks!