From: Jason Wang <jasowang@redhat.com>
To: Amos Kong <akong@redhat.com>, virtualization@lists.linux-foundation.org
Cc: netdev@vger.kernel.org, mst@redhat.com
Subject: Re: [PATCH] virtio_net: zero is an invald queue_pairs number
Date: Mon, 21 Apr 2014 14:45:25 +0800 [thread overview]
Message-ID: <5354BE85.5030604@redhat.com> (raw)
In-Reply-To: <5354BB94.4030908@redhat.com>
On 04/21/2014 02:32 PM, Jason Wang wrote:
> On 04/18/2014 01:45 PM, Amos Kong wrote:
>> Execute "ethtool -L eth0 combined 0" in guest, if multiqueue
>> is enabled, virtnet_send_command() will return -EINVAL error,
>> there is a validation in QEMU.
>>
>> But if multiqueue is disabled, virtnet_set_queues() will just
>> return zero (success). We should return error for this situation.
>>
>> Signed-off-by: Amos Kong <akong@redhat.com>
>> ---
>> drivers/net/virtio_net.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
>> index 7b68746..8a852b5 100644
>> --- a/drivers/net/virtio_net.c
>> +++ b/drivers/net/virtio_net.c
>> @@ -1285,7 +1285,7 @@ static int virtnet_set_channels(struct net_device *dev,
>> if (channels->rx_count || channels->tx_count || channels->other_count)
>> return -EINVAL;
>>
>> - if (queue_pairs > vi->max_queue_pairs)
>> + if (queue_pairs > vi->max_queue_pairs || queue_pairs == 0)
>> return -EINVAL;
>>
>> get_online_cpus();
> Acked-by: Jason Wang <jasowang@redhat.com>
Looking at virtnet_set_queues(), it will return success even if no cvq
and no mq support. This is wrong. We need return error in this case.
We'd better fix it and check the its return value in virtnet_restore().
With this fix, there's no need for us to check queue_pairs against zero
like what this patch does.
next prev parent reply other threads:[~2014-04-21 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 5:45 [PATCH] virtio_net: zero is an invald queue_pairs number Amos Kong
2014-04-21 6:32 ` Jason Wang
2014-04-21 6:45 ` Jason Wang [this message]
2014-04-21 15:03 ` Amos Kong
2014-04-22 20:01 ` David Miller
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=5354BE85.5030604@redhat.com \
--to=jasowang@redhat.com \
--cc=akong@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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).