linux-kernel - Re: linux-next: Fixes tag needs some work in the bpf-next tree

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: <CAADnVQJsGudS7W=GcJGQyrzwsZ26=uCDQUW7MGDZ-RVpdsOH6A@mail.gmail.com>
Date:   Wed, 24 Aug 2022 17:56:24 -0700
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Kumar Kartikeya Dwivedi <memxor@...il.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Daniel Borkmann <daniel@...earbox.net>,
        Alexei Starovoitov <ast@...nel.org>,
        Andrii Nakryiko <andrii@...nel.org>, bpf <bpf@...r.kernel.org>,
        Networking <netdev@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the bpf-next tree

On Wed, Aug 24, 2022 at 10:05 AM Kumar Kartikeya Dwivedi
<memxor@...il.com> wrote:
>
> On Wed, 24 Aug 2022 at 07:00, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > Hi all,
> >
> > In commit
> >
> >   2e5e0e8ede02 ("bpf: Fix reference state management for synchronous callbacks")
> >
> > Fixes tag
> >
> >   Fixes: 69c87ba6225 ("bpf: Add bpf_for_each_map_elem() helper")
> >
> > has these problem(s):
> >
> >   - Target SHA1 does not exist
> >
> > Maybe you meant
> >
> > Fixes: 69c087ba6225 ("bpf: Add bpf_for_each_map_elem() helper")
> >
>
> Ugh, really sorry, I must have fat fingered and pressed 'x' in vim
> while editing the commit message. I always generate these using a git
> fixes alias.

Since that was caught quickly there weren't that many commits on top.
Fixed and force pushed bpf-next.

We actually have a script that checks such sha-s. Not sure how we missed it.