From: P J P <ppandit@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
Azureyang <azureyang@tencent.com>
Subject: Re: [Qemu-devel] [PATCH] net: virtio-net: initialise local 'netcfg' variable
Date: Mon, 5 Dec 2016 14:40:47 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.2.20.1612051428330.11292@wniryva> (raw)
In-Reply-To: <b7b1dcab-b187-6f2b-853b-5b27dc1d1d04@redhat.com>
Hello Jason,
+-- On Mon, 5 Dec 2016, Jason Wang wrote --+
| > diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
| > index 01f1351..cb5b3dc 100644
| > --- a/hw/net/virtio-net.c
| > +++ b/hw/net/virtio-net.c
| > @@ -72,7 +72,7 @@ static int vq2q(int queue_index)
| > static void virtio_net_get_config(VirtIODevice *vdev, uint8_t *config)
| > {
| > VirtIONet *n = VIRTIO_NET(vdev);
| > - struct virtio_net_config netcfg;
| > + struct virtio_net_config netcfg = {};
| >
| > virtio_stw_p(vdev, &netcfg.status, n->status);
| > virtio_stw_p(vdev, &netcfg.max_virtqueue_pairs, n->max_queues);
|
| Good catch but since mtu patch wasn't accepted so mtu were in fact not exposed
| to guest.
'mtu' appears to have been added by commit 'dbdfea9226c9d0bdd', could you
pleae confirm?
| (FYI, you can have a look at Maxime patch, he did a stw_p here()).
+ virtio_stw_p(vdev, &netcfg.mtu, n->mtu);
+
Yes, but this isn't accepted yet, is it?
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2016-12-05 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 11:28 [Qemu-devel] [PATCH] net: virtio-net: initialise local 'netcfg' variable P J P
2016-12-05 7:48 ` Jason Wang
2016-12-05 9:10 ` P J P [this message]
2016-12-05 9:43 ` Jason Wang
2016-12-05 10:30 ` P J P
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.20.1612051428330.11292@wniryva \
--to=ppandit@redhat.com \
--cc=azureyang@tencent.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).