netdev - Re: linux-next: Tree for January 19 (vhost

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] [day] [month] [year] [list]

Message-Id: <20100120074815.ceff3a44.randy.dunlap@oracle.com>
Date:	Wed, 20 Jan 2010 07:48:15 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	"Michael S. Tsirkin" <mst@...hat.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	netdev <netdev@...r.kernel.org>, linux-next@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for January 19 (vhost_net)

On Wed, 20 Jan 2010 13:33:41 +0200 Michael S. Tsirkin wrote:

> On Tue, Jan 19, 2010 at 10:41:39AM -0800, Randy Dunlap wrote:
> > On Tue, 19 Jan 2010 18:10:41 +1100 Stephen Rothwell wrote:
> > 
> > > Hi all,
> > > 
> > > Changes since 20100118:
> > 
> > 
> > When CONFIG_TUN is not enabled:
> > 
> > drivers/built-in.o: In function `get_socket':
> > net.c:(.text+0x2899a3): undefined reference to `tun_get_socket'
> > 
> > 
> > so VHOST_NET can either depend on TUN or select TUN, but if it
> > selects TUN, it will also need to select CRC32.
> > 
> > ---
> > ~Randy
> 
> Just to clarify sure, the broken configuration is VHOST=y TUN=m, I sent
> a fixup patch to forbid that configuration.  But both VHOST=y TUN=n and
> VHOST=m TUN=n build fine for me on linux-next (commit
> af2b07e7e0a9c6bf82ce4d6a77f0412ae54f575b).  Randy, could you please
> confirm that VHOST=y TUN=m is what you tested, or alternatively make
> your .config available to me so I can reproduce the problem?

Hi Michael,

You are correct, VHOST_NET=y, TUN=m.

Thanks.
---
~Randy
--
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