netdev - Re: [PATCH RFC] tun: export underlying socket

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]

Date:	Tue, 15 Sep 2009 16:18:39 +0300
From:	"Michael S. Tsirkin" <mst@...hat.com>
To:	Or Gerlitz <or.gerlitz@...il.com>
Cc:	Or Gerlitz <ogerlitz@...taire.com>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	herbert@...dor.apana.org.au
Subject: Re: [PATCH RFC] tun: export underlying socket

On Tue, Sep 15, 2009 at 04:11:22PM +0300, Or Gerlitz wrote:
> On 9/14/09, Michael S. Tsirkin <mst@...hat.com> wrote:
> >> 3. for tun fd
> >> VM.TX is translated by vhost to sendmsg which is translated by tun to
> >> netif_rx which is then handled by the bridge
> >> NIC RX  goes to the bridge which xmits the packet a tun interface, now
> >> what makes tun provide this packet to vhost and how it is done?
> 
> > Same as above. vhost polls tun and calls recvmsg on the socket
> 
> no, correct if I'm wrong, but recvmsg calls tun_do_read and the later
> calls tun_put_user to the packet goes to user space and not into the virtq
> 
> Or.

It ends up in the virtq because that maps userspace addresses.
This is the same as with packet sockets, really.

-- 
MST
--
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