netdev - Re: confused pw-bot. Re: pull-request: bpf-next 2022-02-17

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, 17 Feb 2022 19:58:50 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc:     Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
        patchwork-bot+netdevbpf@...nel.org,
        Daniel Borkmann <daniel@...earbox.net>,
        "David S. Miller" <davem@...emloft.net>,
        Alexei Starovoitov <ast@...nel.org>,
        Andrii Nakryiko <andrii@...nel.org>,
        Network Development <netdev@...r.kernel.org>,
        bpf <bpf@...r.kernel.org>
Subject: Re: confused pw-bot. Re: pull-request: bpf-next 2022-02-17

On Thu, 17 Feb 2022 18:20:07 -0800 Alexei Starovoitov wrote:
> On Thu, Feb 17, 2022 at 5:46 PM Jakub Kicinski <kuba@...nel.org> wrote:
> >
> > On Fri, 18 Feb 2022 01:45:56 +0000 patchwork-bot+netdevbpf@...nel.org
> > wrote:  
> > > Hello:
> > >
> > > This pull request was applied to bpf/bpf.git (master)  
> >
> > :/ gave me a scare. No, it's not pushed, yet, still building.  

Pushed now.

> Wow. pw-bot gots things completely wrong :)
> 
> It replied to Daniel's bpf-next PR with:
> "
> This pull request was applied to bpf/bpf.git (master)
> by Jakub Kicinski <kuba@...nel.org>:
> 
> Here is the summary with links:
>   - pull-request: bpf-next 2022-02-17
>     https://git.kernel.org/bpf/bpf/c/7a2fb9128515
> "
> that link points to my bpf PR that Jakub landed 8 hours earlier
> into net tree.
> 
> I ffwded bpf tree half an hour ago.
> I guess that's what confused the bot.
> 
> Konstanin, please take a look.

Presumably PRs should be quite trivial thing to handle since:

  for you to fetch changes up to d24d2a2b0a81dd5e9bb99aeb4559ec9734e1416f:
                                 ^^^^^^^^^^^^
                                 this
ends up:

commit a3fc4b1d09d99cdb6a7dbba5a753db15a10b2e9c
Merge: 2aed49da6c08 d24d2a2b0a81 <= here
                    ^^^^^^^^^^^^
Author: Jakub Kicinski <kuba@...nel.org>
Date:   Thu Feb 17 17:23:51 2022

    Merge https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next
    
    Daniel Borkmann says:
    
    ====================
    bpf-next 2022-02-17


I'm curious if there's something I'm missing, or it's simply a matter 
of the unrelenting finiteness of a working day :)