netdev - Re: [PATCH 2/4] virtio_net: Add a virtqueue for outbound control commands

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1231948868.7109.288.camel@lappy>
Date:	Wed, 14 Jan 2009 09:01:08 -0700
From:	Alex Williamson <alex.williamson@...com>
To:	Mark McLoughlin <markmc@...hat.com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>, kvm <kvm@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH 2/4] virtio_net: Add a virtqueue for outbound control
 commands

On Wed, 2009-01-14 at 10:15 +0000, Mark McLoughlin wrote:
> On Tue, 2009-01-13 at 14:23 -0700, Alex Williamson wrote:
> > This will be used for RX mode, MAC filter table, VLAN filtering, etc...
> 
> Looks very reasonable. I'm a bit wary of send_command() being
> synchronous, but it probably makes sense.

Yes, I tried to make it async, but quickly ran into problems sleeping
when I wasn't allowed to.  Using it in this way does pretty much limit
it to an outbound channel though... all worthy of commit log comments.

> > +static int virtnet_send_command(struct virtnet_info *vi, u8 class, u8 cmd,
> > +				void *data, unsigned int len)
> > +{
> > +	struct scatterlist sg[3];
> > +	struct {
> > +		u8 class;
> > +		u8 cmd;
> > +	} ctrl_cmd;
> 
> I'd like to see this defined in virtio_net_hdr.

As part of struct virtio_net_hdr?  I'm not sure what that'd buy us and
would likely break compatibility.  Or do you simply mean defined in
virtio-net.h?

> Why the need for class/cmd? Why not just a single 16 bit command field?

It seemed like a good way to logically divide up an address space and
makes it easy for the backend to break up the code so it doesn't become
a huge table.

> > +	u8 ctrl_status;
> > +	unsigned int tmp;
> > +	int i = 0;
> > +
> > +	if (!vi->cvq)
> > +		return -EFAULT;
> 
> BUG_ON() probably makes more sense here.

This is to allow a newer virtio_net guest driver to run on an old qemu.
That's why I don't generate a fatal error if we don't find the control
queue.  In that case the backend will be running in promiscuous mode and
I think all of these commands can safely fail.  Thanks for the comments.

Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html