Re: [Qemu-stable] Patch Round-up for stable 1.3.1, freeze Monday

[mdroth]

On Wed, Jan 16, 2013 at 10:12:38PM +0400, Michael Tokarev wrote:
> 16.01.2013 20:49, Michael Roth wrote:
> >Hi everyone,
> >
> >The following new patches are queued for QEMU stable v1.3.1:
> >
> >https://github.com/mdroth/qemu/commits/stable-1.3-staging
> >
> >The release is planned for 01-25-2013:
> >
> >http://wiki.qemu.org/Planning/1.3
> >
> >Please CC address@hidden on any patches you think should be
> >included in the release. The cut-off date is 01-21-2013 for new patches.
> >
> >Testing/feedback is greatly appreciated.
> >
> >Thanks!
> 
> Actual commit IDs from the master branch, with some comments
> (with just one useful for 1.3 comment, about e1000 security fix):
> 
> >204dd38 raw-posix: fix bdrv_aio_ioctl (Paolo Bonzini)
> b608c8dc02c78ee95455a0989bdf1b41c768b2ef
> 
> >86bab45 vfio-pci: Loosen sanity checks to allow future features (Alex 
> >Williamson)
> 8fc94e5a8046e349e07976f9bcaffbcd5833f3a2
> 
> >006c747 pci-assign: Enable MSIX on device to match guest (Alex Williamson)
> feb9a2ab4b0260d8d680a7ffd25063dafc7ec628
> 
> This is applicable to old qemu-kvm (pre-1.3-merge), so it is qemu-kvm 1.1
> and qemu-kvm 1.2.  I missed it for 1.1 because it is qemu-kvm-specific.
> Queued for debian qemu-kvm package.
> 
> >f042cca vfio-pci: Make host MSI-X enable track guest (Alex Williamson)
> b0223e29afdc88cc262a764026296414396cd129
> 
> >1205b80 target-xtensa: fix search_pc for the last TB opcode (Max Filippov)
> 36f25d2537c40c6c47f4abee5d31a24863d1adf7
> 
> Now queued to stable-1.1 too.
> 
> >ff0c079 buffered_file: do not send more than s->bytes_xfer bytes per tick 
> >(Paolo Bonzini)
> bde54c08b4854aceee3dee25121a2b835cb81166
> 
> Now queued to stable-1.1 too, with backport changes.
> 
> >d745511 migration: fix migration_bitmap leak (Paolo Bonzini)
> 244eaa7514a944b36273eb8428f32da8e9124fcf
> 
> >5afd0ec e1000: Discard oversized packets based on SBP|LPE (Michael Contreras)
> 2c0331f4f7d241995452b99afaf0aab00493334a
> 
> Guys, this is just one half of the CVE-2012-6075 fix.
> Please don't repeat the same mistake again and again.
> Second patch by Michael is neede to fix this too.

Do you mean b0d9ffcd0251161c7c92f94804dcf599dfa3edeb? If so, that one made it
in just before 1.3.0, and this picks up the 2nd patch.