netdev - Re: Problems with VSOCK?

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: <2319583.NdTBqk4ibZ@sifl>
Date:	Wed, 20 Feb 2013 17:28:55 -0500
From:	Paul Moore <pmoore@...hat.com>
To:	Andy King <acking@...are.com>
Cc:	netdev@...r.kernel.org
Subject: Re: Problems with VSOCK?

On Wednesday, February 20, 2013 02:19:42 PM Andy King wrote:
> Hi Paul,
> 
> > I'm currently looking at the VSOCK implementation in netdev-next to
> > determine what we need in the way of LSM hooks and I ran into a few
> > things which look rather odd:
> > 
> > * net/vmw_sock/Kconfig
> > 
> > VMWARE_VMCI_SOCKETS depends on VMWARE_VMCI which doesn't look to be
> > defined
> > anywhere, help?  For what it is worth, removing the VMWARE_VMCI dependency
> 
> Ah, I think this is the same problem someone else had a few days ago.  VMCI
> came in via Greg's char-misc-next tree, and it hasn't merged into Dave's
> tree yet.  But the top-level linux-next tree now has all required modules:
> 
> http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=summary
> 
> Sorry about them coming in from different trees :/

Okay, thanks, I'll grab a copy of the next tree and take a look.  That makes 
much more sense, I was finding it hard to believe that so much was missing :)

-- 
paul moore
security and virtualization @ redhat

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