netdev - Re: [PATCH bpf-next v8 00/12] bpf: More sock

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]

Message-ID: <1516808880.3715.20.camel@gmail.com>
Date:   Wed, 24 Jan 2018 07:48:00 -0800
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Alexei Starovoitov <ast@...com>, Lawrence Brakmo <brakmo@...com>,
        netdev <netdev@...r.kernel.org>
Cc:     Kernel Team <kernel-team@...com>, Blake Matheny <bmatheny@...com>,
        Daniel Borkmann <daniel@...earbox.net>,
        Neal Cardwell <ncardwell@...gle.com>,
        Yuchung Cheng <ycheng@...gle.com>
Subject: Re: [PATCH bpf-next v8 00/12] bpf: More sock_ops callbacks

On Wed, 2018-01-24 at 07:27 -0800, Alexei Starovoitov wrote:
> 
> Most of the time, Yes, but it's the other way around this time.
> I specifically asked Larry to do it this way, since net tree is
> practically closed (only critical fixes allowed).
> When 4.15 is released on Sunday we'll send this patch
> independently to 4.15 and 4.14
> 

How hard would it be to put the fix first in the series then ?
If this proves complex, then maybe we have a bigger problem.

I did not know merging bpf into bpf-next would be hard :)


Thanks.