linux-kernel - Re: [GIT PULL] KVM changes for Linux 6.3-rc7

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: <2560f4b4-8620-6160-eee5-4086630bb5cc@redhat.com>
Date:   Tue, 11 Apr 2023 08:34:47 +0200
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, KVM list <kvm@...r.kernel.org>,
        "'oliver.upton@...ux.dev'" <oliver.upton@...ux.dev>
Subject: Re: [GIT PULL] KVM changes for Linux 6.3-rc7

On 4/10/23 23:05, Linus Torvalds wrote:
> On Mon, Apr 10, 2023 at 8:39 AM Paolo Bonzini<pbonzini@...hat.com>  wrote:
>>    https://git.kernel.org/pub/scm/virt/kvm/kvm.git  tags/for-linus
>>
>> for you to fetch changes up to 0bf9601f8ef0703523018e975d6c1f3fdfcff4b9:
>>
>>    Merge tag 'kvmarm-fixes-6.3-3' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD (2023-04-06 13:34:19 -0400)
> Nope, not at all.
> 
> You seem to have tagged the wrong commit. Instead of pointing to that
> "kvmarm fixes" thing, it points to something entirely different.
> 
> Please double-check what happened.

That's the current 6.4 head, so the most likely explanation is that I 
incorrectly ran "git tag ... -F<absolute path> && git push kvm 
+tags/for-linus" again from the wrong window/worktree.  That must have 
been while I was doing a final check of the pull request, between 
preparing the message and sending it; probably something stupid like 
pressing "Enter" instead of "Ctrl-c" after a command line search (for 
example, I typically use Ctrl-r to do the final send without --dry-run).

I've now pushed the correct tag (object hash 7088282073b8).

Out of curiosity, do you have some kind of script that parses the "git 
request-pull" messages and does these checks?  Or was it just the 
mismatch between diffstat and tag message?

Paolo