netdev - Re: [PATCH net 1/1] net: Fix return value of qdisc ingress handling on success

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

Message-ID: <CANn89i+2461VjtW3+_0za87Nq6S3kNsDxU4oDT9YncW6uQ85kA@mail.gmail.com>
Date:   Thu, 22 Sep 2022 16:17:25 -0700
From:   Eric Dumazet <edumazet@...gle.com>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Daniel Borkmann <daniel@...earbox.net>,
        Paul Blakey <paulb@...dia.com>,
        Vlad Buslov <vladbu@...dia.com>, Oz Shlomo <ozsh@...dia.com>,
        Roi Dayan <roid@...dia.com>, netdev <netdev@...r.kernel.org>,
        Saeed Mahameed <saeedm@...dia.com>,
        "David S. Miller" <davem@...emloft.net>,
        Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net 1/1] net: Fix return value of qdisc ingress handling
 on success

On Thu, Sep 22, 2022 at 2:06 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Thu, 22 Sep 2022 08:23:49 -0700 Jakub Kicinski wrote:
> > What I meant is we don't merge fixes into net-next directly.
> > Perhaps that's my personal view, not shared by other netdev maintainers.
>
> FWIW I've seen Eric posting a fix against net-next today
> so I may indeed be the only one who thinks this way :)

If you refer to the TCP fix, this is because the blamed patch is in
net-next only.

These are very specific changes that are unlikely to cause real issues.
Only packetdrill tests were unhappy with the glitches.