Thread (42 messages) 42 messages, 6 authors, 2010-02-18

Re: [PATCH 3/3] net: macvtap driver

From: Arnd Bergmann <arnd@arndb.de>
Date: 2010-01-29 19:50:08
Also in: bridge, lkml

On Friday 29 January 2010, Michael S. Tsirkin wrote:
quoted
That may well be, I haven't tried vlan. What do you think it should do
then?
Look at eth_type for a more complete packet parsing.
ok. I initially called that but it crashed because the skb was not initialized
properly at that point. I'll have a look.
quoted
quoted
quoted
+/*
+ * provide compatibility with generic tun/tap interface
+ */
+static long macvtap_ioctl(struct file *file, unsigned int cmd,
+                   unsigned long arg)
+{
All of these seem to be stubs, and tun has many more that you didn't
stub out. So, why do you bother to support any ioctls at all?
Again, minimum features to get things going. qemu fails to open
the device if these ioctls are not implemented, but any of the
more advanced features are left out.
This is strange, could be application bug.  E.g. send buf size is
relatively new and apps should handle failure gracefully.  IMO,
returning success and ignoring the value is not a good idea.  How about
we just fix qemu?  What about other apps?
Ok, I'll go through the ioctls again and make sure they behave correctly
they way you said. I haven't tried against against anything but qemu and
cat.

	Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help