linux-kernel - Re: [GIT PULL v2] 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] [day] [month] [year] [list]

Message-ID: <20190110152141.GN166797@sasha-vm>
Date:   Thu, 10 Jan 2019 10:21:41 -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 v2] Hyper-V commits for 5.0

On Thu, Jan 10, 2019 at 08:43:23AM +0100, Greg KH wrote:
>On Thu, Jan 10, 2019 at 02:05:46AM -0500, Sasha Levin wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> Hi Greg,
>>
>> 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.
>>
>> - --
>> Thanks,
>> Sasha
>>
>>
>> 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)
>>
>> - ----------------------------------------------------------------
>> hyperv-fixes-signed
>>
>> - ----------------------------------------------------------------
>
>What changed?  In the tag, the above "one line" message is all that is
>there, just like in the first version of this pull request.
>
>That's what I asked to be changed, please put the information you have
>above "Three bug...", in the tag itself.
>
>Then, when I do a 'git pull' I can see that in the changelog message and
>I do not have to go and manually cut/paste from the email, into the git
>commit terminal, the needed information.
>
>As it is, again, only the one line "hyperv-fixes-signed" shows up in the
>commit log when I want to do the pull.
>
>Try it yourself and see what I mean.

Ah, I see. Coming right up.

--
Thanks,
Sasha