On Tue, 6 Feb 2024 19:37:46 +0300 Michael Tokarev wrote:
03.02.2024 12:47, Michael Tokarev wrote:
>>> It looks like we broke suspend/resume in this version of qemu.
>> Oops. Is that related to the cryptsetup failure, or a separate issue?
>
> Yes, it is related to cryptsetup autopkgtest
06.02.2024 20:55, Adam D. Barratt :
On Tue, 2024-02-06 at 20:49 +0300, Michael Tokarev wrote:
..
The change isn't small per se, as the commit is rather large (mostly
due to many changed tests, - it changes order of output in quite some
places). Here's the diffstat:
monitor/qmp.c
On Tue, 2024-02-06 at 20:49 +0300, Michael Tokarev wrote:
> 06.02.2024 20:33, Adam D. Barratt:
> > On Tue, 2024-02-06 at 19:37 +0300, Michael Tokarev wrote:
> > > problematic upstream commit (on master) is this one:
> > >
06.02.2024 20:33, Adam D. Barratt:
On Tue, 2024-02-06 at 19:37 +0300, Michael Tokarev wrote:
problematic upstream commit (on master) is this one:
https://gitlab.com/qemu-project/qemu/-/commit/effd60c878176bcaf97fa7ce2b12d04bb8ead6f7
Technically we already froze p-u for 12.5 on Sunday
On Tue, 2024-02-06 at 19:37 +0300, Michael Tokarev wrote:
> e problematic upstream commit (on master) is this one:
> https://gitlab.com/qemu-project/qemu/-/commit/effd60c878176bcaf97fa7ce2b12d04bb8ead6f7
> It has links to 2 bugs it is fixing, and there are quite a few
> other bugs which are fixed
03.02.2024 12:47, Michael Tokarev wrote:
It looks like we broke suspend/resume in this version of qemu.
Oops. Is that related to the cryptsetup failure, or a separate issue?
Yes, it is related to cryptsetup autopkgtest failure. It looks
like this is the only place where suspend/resume code
On Sat, 2024-02-03 at 12:47 +0300, Michael Tokarev wrote:
> 03.02.2024 12:43, Adam D. Barratt :
> ..
> > > I'm aware of the autopkgtest failure with cryptsetup, working on
> > > it
> > > now.
> > > It looks like we broke suspend/resume in this version of qemu.
> >
> > Oops. Is that related to the
03.02.2024 12:43, Adam D. Barratt :
..
I'm aware of the autopkgtest failure with cryptsetup, working on it
now.
It looks like we broke suspend/resume in this version of qemu.
Oops. Is that related to the cryptsetup failure, or a separate issue?
Yes, it is related to cryptsetup autopkgtest
On Sat, 2024-02-03 at 11:40 +0300, Michael Tokarev wrote:
> 01.02.2024 11:40, Adam D Barratt :
> ..
> > Package: qemu
> > Version: 7.2+dfsg-7+deb12u4
> >
> > Explanation: new upstream stable release; irtio-net: correctly copy
> > vnet header when flushing TX [CVE-2023-6693]; fix null pointer
> >
01.02.2024 11:40, Adam D Barratt :
..
Package: qemu
Version: 7.2+dfsg-7+deb12u4
Explanation: new upstream stable release; irtio-net: correctly copy vnet header
when flushing TX [CVE-2023-6693]; fix null pointer dereference issue
[CVE-2023-6683]
There's a typo here, should be virtio-net.
package release.debian.org
tags 1062044 = bookworm pending
thanks
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian bookworm.
Thanks for your contribution!
Upload details
==
Package: qemu
Version:
11 matches
Mail list logo