linux-kernel - Re: [GIT PULL v3] Hyper-V commits for 5.0

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]

Date:   Fri, 11 Jan 2019 09:10:12 -0500
From:   Sasha Levin <sashal@...nel.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...rosoft.com, kys@...rosoft.com,
        haiyangz@...rosoft.com, sthemmin@...rosoft.com,
        linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL v3] Hyper-V commits for 5.0

On Fri, Jan 11, 2019 at 10:15:52AM +0100, Greg KH wrote:
>On Thu, Jan 10, 2019 at 10:24:31AM -0500, Sasha Levin wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
>>
>>   Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
>>
>> are available in the Git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git tags/hyperv-fixes-signed
>>
>> for you to fetch changes up to b5679cebf780c6f1c2451a73bf1842a4409840e7:
>>
>>   vmbus: fix subchannel removal (2019-01-09 19:20:31 -0500)
>>
>> - ----------------------------------------------------------------
>> Three bug fixes for different parts of the hyper-v code:
>>
>>  - Fix for a lockup when changing NIC's MTU from Dexuan.
>>  - Fix of use of uninitialized memory from Dexuan.
>>  - Fix for memory corruption caused by ballooning from Vitaly.
>>
>> All 3 were tested internally.
>>
>> - ----------------------------------------------------------------
>
>Did you really push out an updated tag?  I still get the following text
>when doing a pull of this tag:
>
>-----------
>hyperv-fixes-signed
>-----------
>
>So it looks like nothing changed from your previous request.
>
>Note, when creating the signed tag, with 'git tag -s' you have to enter
>the text you want to show up in the tag into the editor at that time.

Ugh, I haven't actually pushed it, so while the text appeared on
git-request-pull because it was in my local tag, you didn't see it
because the remote tag with the same name didn't have it.

I've pushed it out and made sure the 'git pull' you'd do looks right.
Sorry!

--
Thanks,
Sasha