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]
Date:   Thu, 28 Oct 2021 11:17:38 +0200
From:   Toke Høiland-Jørgensen <toke@...hat.com>
To:     Daniel Borkmann <daniel@...earbox.net>, davem@...emloft.net
Cc:     kuba@...nel.org, ast@...nel.org, andrii.nakryiko@...il.com,
        netdev@...r.kernel.org, bpf@...r.kernel.org,
        Lorenzo Bianconi <lorenzo.bianconi@...hat.com>
Subject: Re: pull-request: bpf 2021-10-26

Daniel Borkmann <daniel@...earbox.net> writes:

> On 10/28/21 12:03 AM, Toke Høiland-Jørgensen wrote:
>> Daniel Borkmann <daniel@...earbox.net> writes:
>> 
>>> The following pull-request contains BPF updates for your *net* tree.
>>>
>>> We've added 12 non-merge commits during the last 7 day(s) which contain
>>> a total of 23 files changed, 118 insertions(+), 98 deletions(-).
>> 
>> Hi Daniel
>> 
>> Any chance we could also get bpf merged into bpf-next? We'd like to use
>> this fix:
>> 
>>> 1) Fix potential race window in BPF tail call compatibility check,
>>> from Toke Høiland-Jørgensen.
>
> Makes sense! I presume final net tree PR before merge win might go out today
> or tomorrow (Jakub/David?) and would get fast-fwd'ed into net-next after that
> as well, which means we get the current batch for bpf-next out by then. By
> that we'd have mentioned commit in bpf-next after re-sync.

Alright, sounds good - thanks! :)

-Toke

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ