netdev - Re: merge window is open. bpf-next is still open.

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: <20201012110046.3b2c3c27@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Mon, 12 Oct 2020 11:00:46 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc:     Daniel Borkmann <daniel@...earbox.net>, bpf <bpf@...r.kernel.org>,
        Network Development <netdev@...r.kernel.org>,
        Kernel Team <Kernel-team@...com>,
        "David S. Miller" <davem@...emloft.net>
Subject: Re: merge window is open. bpf-next is still open.

On Sun, 11 Oct 2020 17:59:16 -0700 Alexei Starovoitov wrote:
> Hi BPF developers,
> 
> The merge window has just opened.
> Which would typically mean that bpf-next is closing,
> but things are going to be a little bit different this time.
> We're stopping to accept new features into bpf-next/master.
> The few pending patches might get applied and imminent pull-req into
> net-next will be sent.
> After that bpf-next/master will be frozen for the duration of the merge window,
> but bpf-next/next branch will be open for the new features.
> 
> So please continue the BPF development and keep sending your patches.
> They will be reviewed as usual.
> After the merge window everything that is accumulated in bpf-next/next
> will be applied to bpf-next/master.
> Due to merge/rebase sha-s in bpf-next/next will likely be unstable.
> 
> Please focus on fixing bugs that may get exposed during the merge window.
> The bpf tree is always open for bug fixes.

FWIW for CIs switching between bpf-next/next and bpf-next/master could
be somewhat fragile. Since bpf-next/master is frozen during the merge
window, why not apply the patches there?