qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL 00/15] Timer, virtio-scsi-test, build, memory cha


From: Peter Maydell
Subject: Re: [Qemu-devel] [PULL 00/15] Timer, virtio-scsi-test, build, memory changes for 2015-06-19
Date: Fri, 19 Jun 2015 16:34:30 +0100

On 19 June 2015 at 11:19, Peter Maydell <address@hidden> wrote:
> On 19 June 2015 at 08:45, Paolo Bonzini <address@hidden> wrote:
>> The following changes since commit 93f6d1c16036aaf34055d16f54ea770fb8d6d280:
>>
>>   Merge remote-tracking branch 'remotes/kraxel/tags/pull-vga-20150615-1' 
>> into staging (2015-06-16 10:35:43 +0100)
>>
>> are available in the git repository at:
>>
>>   git://github.com/bonzini/qemu.git tags/for-upstream
>>
>> for you to fetch changes up to 4e6ab89110c85f7163b875d9e900e97ab0a175b0:
>>
>>   exec: clamp accesses against the MemoryRegionSection (2015-06-19 09:06:04 
>> +0200)
>>
>> ----------------------------------------------------------------
>> * i8254 security fix
>> * Avoid long 100% CPU wait after restarting guests that use the periodic 
>> timer
>> * Fixes for access clamping (WinXP, MIPS)
>> * wixl/.msi support for qemu-ga on Windows
>
> Hi. I'm afraid this fails to build on 32 bit:
>
> /root/qemu/tests/virtio-scsi-test.c: In function ‘qvirtio_scsi_pci_init’:
> /root/qemu/tests/virtio-scsi-test.c:96:12: error: cast from pointer to
> integer of different size [-Werror=pointer-to-int-cast]

...incidentally, this is a good reason not to throw CVE fixes in
with other patches in a pull request, I think. What we seem to
have done recently is to either (a) directly apply the CVE patch
or (b) provide a single-patch pull request with only the CVE patch,
which means we can put the fixes into master on the day of
disclosure. (That will become more important as a property if we
can get our story for CVE patches on stable branches sorted out...)

thanks
-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]