linux-kernel - Re: linux-next: Tree for Sep 16

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: <81FAEBB3-FE85-49B4-BE31-68779D92C0B9@gmail.com>
Date:   Thu, 16 Sep 2021 19:53:59 -0300
From:   Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
CC:     Alexei Starovoitov <alexei.starovoitov@...il.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Andrii Nakryiko <andrii@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Jiri Olsa <jolsa@...nel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Sep 16



On September 16, 2021 7:49:12 PM GMT-03:00, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>Hi all,
>
>On Thu, 16 Sep 2021 18:43:37 -0300 Arnaldo Carvalho de Melo <arnaldo.melo@...il.com> wrote:
>>
>> On September 16, 2021 2:30:04 PM GMT-03:00, Alexei Starovoitov <alexei.starovoitov@...il.com> wrote:
>> >On Wed, Sep 15, 2021 at 11:11 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:  
>> >>
>> >> Changes since 20210915:
>> >>
>> >> The bpf-next tree still had its build failure so I used the version from
>> >> next-20210913.  
>> >
>> >Arnaldo,
>> >
>> >could you please push Andrii's fix into your tree asap
>> >and then cleanup/follow up with a better fix if  necessary?  
>> 
>> It's there since yesterday:
>> 
>> https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core&id=00e0ca3721cf2ddcb38cf676a3de61933640d31d
>> 
>> Replying just now since it's a holiday here and I was AFK.
>
>But that is not in any tree that is included in linux-next (and when it
>does appear, it will be in the tip tree 

Nope, perf tools don't transit via tip for quite a while already, it goes to Linus directly.

Would it be possible to have it included in linux-next? I.e. perf/core in my repo is what should go to the next Linux release, perf/urgent goes to the current merge window, just like tip.

- Arnaldo

which gets merged well after
>the bpf-next tree).  I will include that patch as a merge fix up for
>the bpf-next tree until that patch has gone into Linus' tree ... so,
>someone has to ensure that this patch get into Linus tree *before* the
>bpf-next tree.
>
>So, do you see the problem?  Linus' tree is fine on its own.  The
>bpf-next tree has a patch that breaks Linus' tree, but the breakage is
>not seen in the bpf-next tree because it is base on v5.14 and the
>interacting patch is in v5.15-rc1.