Re: Fixing tap(4) behaviour

["Arnaud Lacombe" <lacombar%gmail.com@localhost>]

On Sat, Nov 29, 2008 at 3:21 PM, Quentin Garnier <cube%cubidou.net@localhost> 
wrote:
> On Sat, Nov 29, 2008 at 03:05:46PM -0500, Arnaud Lacombe wrote:
>> Hi Folks,
>>
>> People currently using qemu(1) need to use a dirty static fd-based
>> trick to link the created interface to qemu(1). This is due to the
>> fact that 1) qemu doesn't check the return value of the stat(2)
>> syscall and 2) our tap(4) cloner device provide nothing to know the
>> created interface's unit. I fixed this by making the cloner device
>
> That's not true.  You should have read tap(4)'s manual page.
true, my bad.

> Besides,
> I have always told people how qemu was supposed to do that, and I think
> that someone had actually made a patch for qemu at some point but I
> guess it was lost.
>
Only FreeBSD and us have implemented TAPGIFNAME.

Beside that, this do not solve the problem of the behavior of the
stat(2) syscall on a cloner device.

 - Arnaud