This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/338
** Changed in: qemu
Status: In Progress => Expired
**
Took a look at the patch today, I think it might need a change or two
but it should be quick to do. I've asked Thomas to move this issue to
gitlab so I can keep a closer eye on it.
--js
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
** Changed in: qemu
Status: New => In Progress
** Changed in: qemu
Importance: Undecided => High
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1912780
Title:
QEMU: Null Pointer Failure
Upstream patch:
-> https://lists.nongnu.org/archive/html/qemu-devel/2021-01/msg05986.html
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
