[v1] NEWS: Document my contributions for upcoming release

[PATCH] NEWS: Document my contributions for upcoming release

Michal Privoznik posted 1 patch 7 months, 1 week ago

Diff against v1 v1 v1 v1 v1 v1 v1 v1 v1 v1 v1 v2
Download mbox

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/libvirt tags/patchew/2c8e332c96ee8c20c0f66abd5d6c2301521cc044.1695972180.git.mprivozn@redhat.com

There is a newer version of this series

NEWS.rst | 12 ++++++++++++
1 file changed, 12 insertions(+)

Expand all Fold all

[PATCH] NEWS: Document my contributions for upcoming release

Posted by Michal Privoznik 7 months, 1 week ago

Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
---
 NEWS.rst | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/NEWS.rst b/NEWS.rst
index c17a1d002d..6f46e86ba8 100644
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -43,8 +43,20 @@ v9.8.0 (unreleased)
     stability of qemu. Therefore, when available, libvirt will use nbdkit as a
     backend for these network disks and export an NBD disk to qemu.
 
+  * virnetdevopenvswitch: Propagate OVS error messages
+
+    When configuring OVS interfaces/bridges libvirt used to report its own
+    error messages instead of passing (more accurate) error messages from
+    `ovs-vsctl`. This is now changed.
+
 * **Bug fixes**
 
+  * Various virtio-mem/virtio-pmem fixes
+
+    It was discovered that libvirt did not validate some values wrt virtio-mem
+    and virtio-pmem memory devices, e.g. overlapping memory addresses or
+    alignment.
+
 
 v9.7.0 (2023-09-01)
 ===================
-- 
2.41.0

Re: [PATCH] NEWS: Document my contributions for upcoming release

Posted by Ján Tomko 7 months ago

On a Friday in 2023, Michal Privoznik wrote:
>Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
>---
> NEWS.rst | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
>diff --git a/NEWS.rst b/NEWS.rst
>index c17a1d002d..6f46e86ba8 100644
>--- a/NEWS.rst
>+++ b/NEWS.rst
>@@ -43,8 +43,20 @@ v9.8.0 (unreleased)
>     stability of qemu. Therefore, when available, libvirt will use nbdkit as a
>     backend for these network disks and export an NBD disk to qemu.
>
>+  * virnetdevopenvswitch: Propagate OVS error messages
>+
>+    When configuring OVS interfaces/bridges libvirt used to report its own
>+    error messages instead of passing (more accurate) error messages from
>+    `ovs-vsctl`. This is now changed.
>+
> * **Bug fixes**
>
>+  * Various virtio-mem/virtio-pmem fixes
>+
>+    It was discovered that libvirt did not validate some values wrt virtio-mem
>+    and virtio-pmem memory devices, e.g. overlapping memory addresses or
>+    alignment.
>+
>

I think this is an improvement, not a bug fix. There was no broken
functionality before.

Also, instead of saying what was discovered, it would be nice to
describe the new behavior, i.e.

Now libvirt validates more values of virtio-mem and virtio-pmem devices,
e.g. overlapping memory addresses or alignment.

Reviewed-by: Ján Tomko <jtomko@redhat.com>

Jano